Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c77118e79c7c474414750a4c6c8112506a7c0cfa7ca38b3c6911b45bf4425dbd

Tx prefix hash: 6ebb2751081226116c8ac8a3f2f056d59d608f23a7a4d71a141b8eeff1f2eb44
Tx public key: 3d2b60756fb309a3d78700dabeebbb6a7b2df2cb4afd51cb6d56e6cd0aef9906
Timestamp: 1701128917 Timestamp [UCT]: 2023-11-27 23:48:37 Age [y:d:h:m:s]: 00:352:09:57:13
Block: 901108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252337 RingCT/type: yes/0
Extra: 013d2b60756fb309a3d78700dabeebbb6a7b2df2cb4afd51cb6d56e6cd0aef990602110000000575e3f0e9000000000000000000

1 output(s) for total of 0.634242164000 dcy

stealth address amount amount idx
00: 8ef16d56d0991aef8731a2c7916080873a5b67351450ff6092a6c63201aaf774 0.634242164000 1357639 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": 901118, "vin": [ { "gen": { "height": 901108 } } ], "vout": [ { "amount": 634242164, "target": { "key": "8ef16d56d0991aef8731a2c7916080873a5b67351450ff6092a6c63201aaf774" } } ], "extra": [ 1, 61, 43, 96, 117, 111, 179, 9, 163, 215, 135, 0, 218, 190, 235, 187, 106, 123, 45, 242, 203, 74, 253, 81, 203, 109, 86, 230, 205, 10, 239, 153, 6, 2, 17, 0, 0, 0, 5, 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