Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: a2a476115921f051d3ec0e6c15c538a01501e6c88c53d8174504a33abc4617bf

Tx prefix hash: 3ff953b4dc98be28a2f464961eb4ceec42ed4bc2f392c53f90041b94cee5af02
Tx public key: 3530e35eddabea1dfa9de8f86e81cf1a028e3258cdd8fafb0c6944e558cd21dc
Timestamp: 1701977155 Timestamp [UCT]: 2023-12-07 19:25:55 Age [y:d:h:m:s]: 02:033:01:29:32
Block: 908139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 543442 RingCT/type: yes/0
Extra: 013530e35eddabea1dfa9de8f86e81cf1a028e3258cdd8fafb0c6944e558cd21dc02110000000d75e3f0e9000000000000000000

1 output(s) for total of 0.601116263000 dcy

stealth address amount amount idx
00: f0280799edc7d090a444f9527f1999ef1750768e567ec75e40151edb8ce118a9 0.601116263000 1365164 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 908149, "vin": [ { "gen": { "height": 908139 } } ], "vout": [ { "amount": 601116263, "target": { "key": "f0280799edc7d090a444f9527f1999ef1750768e567ec75e40151edb8ce118a9" } } ], "extra": [ 1, 53, 48, 227, 94, 221, 171, 234, 29, 250, 157, 232, 248, 110, 129, 207, 26, 2, 142, 50, 88, 205, 216, 250, 251, 12, 105, 68, 229, 88, 205, 33, 220, 2, 17, 0, 0, 0, 13, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8