Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81e21b459c722ec4c86f3d68113a339b67cb835ca5143c922e7e8ecdd354a822

Tx prefix hash: cabf528eba7dfff1bc872968d49bdfc1229d075b7619c4f471267adb7bc7af8b
Tx public key: 9c2b15d890f4c5ec0c27dc9034e7b61c73ce09e524bfbc4014fa0724402d5f91
Timestamp: 1714712855 Timestamp [UCT]: 2024-05-03 05:07:35 Age [y:d:h:m:s]: 01:187:10:54:47
Block: 1013727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392582 RingCT/type: yes/0
Extra: 019c2b15d890f4c5ec0c27dc9034e7b61c73ce09e524bfbc4014fa0724402d5f910211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e9fb0344c75e632a125a80429a2288edc68eda34f73405f0be994a93f49f979 0.600000000000 1476622 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": 1013737, "vin": [ { "gen": { "height": 1013727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e9fb0344c75e632a125a80429a2288edc68eda34f73405f0be994a93f49f979" } } ], "extra": [ 1, 156, 43, 21, 216, 144, 244, 197, 236, 12, 39, 220, 144, 52, 231, 182, 28, 115, 206, 9, 229, 36, 191, 188, 64, 20, 250, 7, 36, 64, 45, 95, 145, 2, 17, 0, 0, 0, 4, 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