Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75c792f54008c74bd8a74c5c457d3cf6bc8cf2d3f6fe1fd0afcb352d1a9fa535

Tx prefix hash: 70ad65b6aefe67eb753a1132285e9bf328f3e284eccd312c0d92d63ccd0e7cfb
Tx public key: 9964a91bc79abc2398e89259f65485e260f2fa6d25c573b20afde682516b46de
Timestamp: 1719210930 Timestamp [UCT]: 2024-06-24 06:35:30 Age [y:d:h:m:s]: 00:268:04:48:30
Block: 1051006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191665 RingCT/type: yes/0
Extra: 019964a91bc79abc2398e89259f65485e260f2fa6d25c573b20afde682516b46de02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 921dd14ae910465c477f437c429dc730c207ae3383f09e31accddfe62946c025 0.600000000000 1521185 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": 1051016, "vin": [ { "gen": { "height": 1051006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "921dd14ae910465c477f437c429dc730c207ae3383f09e31accddfe62946c025" } } ], "extra": [ 1, 153, 100, 169, 27, 199, 154, 188, 35, 152, 232, 146, 89, 246, 84, 133, 226, 96, 242, 250, 109, 37, 197, 115, 178, 10, 253, 230, 130, 81, 107, 70, 222, 2, 17, 0, 0, 0, 4, 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