Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b391e84ff4f75a4275c86fbaa6c366ec4e7943025ef2a0b0517d804237ff6a4

Tx prefix hash: 1822de70013cbe5abea03a449ff501ee7fcdfa8e1d0dc2db0da71e5a4f45559e
Tx public key: 108d8a508642c8f70e2cf3f1bef956d358fe27e91bd9aff101b59d211a5b7f76
Timestamp: 1717675715 Timestamp [UCT]: 2024-06-06 12:08:35 Age [y:d:h:m:s]: 00:338:21:53:55
Block: 1038292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242225 RingCT/type: yes/0
Extra: 01108d8a508642c8f70e2cf3f1bef956d358fe27e91bd9aff101b59d211a5b7f760211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98ee79f7e580c2de60566e3784ca015c7b56475d84ae4e293f836b0e9a434289 0.600000000000 1506853 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": 1038302, "vin": [ { "gen": { "height": 1038292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98ee79f7e580c2de60566e3784ca015c7b56475d84ae4e293f836b0e9a434289" } } ], "extra": [ 1, 16, 141, 138, 80, 134, 66, 200, 247, 14, 44, 243, 241, 190, 249, 86, 211, 88, 254, 39, 233, 27, 217, 175, 241, 1, 181, 157, 33, 26, 91, 127, 118, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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