Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dc45a015f723f39b6bdce731eaa15326144c0b05edf164f1a77b033ea15fc57

Tx prefix hash: a2557b9b2d7e3381bc3b2252ca4ac1434350f4bb6a675192795b40fb0f237d3b
Tx public key: b97c2811f84de4aa85eb37f79635a386ee6697fb0cc1c0f37af1b33ef3290791
Timestamp: 1718397321 Timestamp [UCT]: 2024-06-14 20:35:21 Age [y:d:h:m:s]: 00:170:14:54:01
Block: 1044277 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122101 RingCT/type: yes/0
Extra: 01b97c2811f84de4aa85eb37f79635a386ee6697fb0cc1c0f37af1b33ef329079102110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e91157f79e210e9d1419a7a6971d54b75f50ffc7885119dbf564cd1b32b12d0 0.600000000000 1513542 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": 1044287, "vin": [ { "gen": { "height": 1044277 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e91157f79e210e9d1419a7a6971d54b75f50ffc7885119dbf564cd1b32b12d0" } } ], "extra": [ 1, 185, 124, 40, 17, 248, 77, 228, 170, 133, 235, 55, 247, 150, 53, 163, 134, 238, 102, 151, 251, 12, 193, 192, 243, 122, 241, 179, 62, 243, 41, 7, 145, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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