Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8e593d521be28e0cec86995305c67fe152dd91ae5d9f1fdee757d07b2a65584

Tx prefix hash: 71ba86d981eaacd7788664afcf176ffc6bbcf995f443a1c8c1365bd5e258bb6e
Tx public key: 0d40691a37b465ffdb501acf869662d7f34aea80c7e2cbb1004226baaf8d08c0
Timestamp: 1715414363 Timestamp [UCT]: 2024-05-11 07:59:23 Age [y:d:h:m:s]: 01:186:12:10:44
Block: 1019566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391889 RingCT/type: yes/0
Extra: 010d40691a37b465ffdb501acf869662d7f34aea80c7e2cbb1004226baaf8d08c002110000000441ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35ca0db1af29178a6a31d56c3e7e275e0611a08c0c6b1fcdbf2aa94ce8e23390 0.600000000000 1483571 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": 1019576, "vin": [ { "gen": { "height": 1019566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35ca0db1af29178a6a31d56c3e7e275e0611a08c0c6b1fcdbf2aa94ce8e23390" } } ], "extra": [ 1, 13, 64, 105, 26, 55, 180, 101, 255, 219, 80, 26, 207, 134, 150, 98, 215, 243, 74, 234, 128, 199, 226, 203, 177, 0, 66, 38, 186, 175, 141, 8, 192, 2, 17, 0, 0, 0, 4, 65, 238, 28, 155, 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