Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5861fd2a717c4976ede7cfe745e64d9fe8abff837bf2f1ce641857ca804494ec

Tx prefix hash: 478b2ca267013cfeabef312f177bff8773d5a42f58c6930eafffa2ec322848d4
Tx public key: d6491b58ef63f26b8480f87333f0873e1e3ff58d1d94595adc5e0c1e6d1c0ac1
Timestamp: 1714370356 Timestamp [UCT]: 2024-04-29 05:59:16 Age [y:d:h:m:s]: 00:305:15:38:49
Block: 1010878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218475 RingCT/type: yes/0
Extra: 01d6491b58ef63f26b8480f87333f0873e1e3ff58d1d94595adc5e0c1e6d1c0ac102110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f8232c8a5a68797fc8039651524ba688afea5425810c8df5486cb910631d28e 0.600000000000 1472952 of 15

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": 1010888, "vin": [ { "gen": { "height": 1010878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f8232c8a5a68797fc8039651524ba688afea5425810c8df5486cb910631d28e" } } ], "extra": [ 1, 214, 73, 27, 88, 239, 99, 242, 107, 132, 128, 248, 115, 51, 240, 135, 62, 30, 63, 245, 141, 29, 148, 89, 90, 220, 94, 12, 30, 109, 28, 10, 193, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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