Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9027114c37367a81d16b0b39bf228d9911b7c9e59643894106841dc139d7ed31

Tx prefix hash: c25cb7edb88d0375bf30db3f26ceb1c2c76480904a32e58e7e07a76a3347d9a3
Tx public key: 33cbf724eed85a0bca69fc131448a0b8ce42f3dfc17024fe7e921451b8cd0b2f
Timestamp: 1704043770 Timestamp [UCT]: 2023-12-31 17:29:30 Age [y:d:h:m:s]: 01:149:10:45:44
Block: 925265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367969 RingCT/type: yes/0
Extra: 0133cbf724eed85a0bca69fc131448a0b8ce42f3dfc17024fe7e921451b8cd0b2f0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e1dd96444c1202487c96b0d5582dccce732ad5fd955479b9b0ae853e29f9975 0.600000000000 1383025 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": 925275, "vin": [ { "gen": { "height": 925265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e1dd96444c1202487c96b0d5582dccce732ad5fd955479b9b0ae853e29f9975" } } ], "extra": [ 1, 51, 203, 247, 36, 238, 216, 90, 11, 202, 105, 252, 19, 20, 72, 160, 184, 206, 66, 243, 223, 193, 112, 36, 254, 126, 146, 20, 81, 184, 205, 11, 47, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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