Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9b716a212eef9f7b3a5beb019dc6aebc0640175858fe4fe752a158c4d54d777

Tx prefix hash: 700c645284318f3e38ffcd6cad6876d53b7fb6b60cc19c9b879e69a20b38773c
Tx public key: 45b54843e42c0238137466f735e2fe59c22c292067ec9e342daa0bb228da993c
Timestamp: 1730560760 Timestamp [UCT]: 2024-11-02 15:19:20 Age [y:d:h:m:s]: 00:143:16:31:55
Block: 1145019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102514 RingCT/type: yes/0
Extra: 0145b54843e42c0238137466f735e2fe59c22c292067ec9e342daa0bb228da993c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 669ac6e9620f2a4cf14fcefd9a1f2cbbedfd5a518f7fa10add311ca65e83e7b0 0.600000000000 1629380 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": 1145029, "vin": [ { "gen": { "height": 1145019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "669ac6e9620f2a4cf14fcefd9a1f2cbbedfd5a518f7fa10add311ca65e83e7b0" } } ], "extra": [ 1, 69, 181, 72, 67, 228, 44, 2, 56, 19, 116, 102, 247, 53, 226, 254, 89, 194, 44, 41, 32, 103, 236, 158, 52, 45, 170, 11, 178, 40, 218, 153, 60, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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