Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f90d1e8bdd417f2b087483ed681867f4d7396dbd338dba194cda277f0507cf91

Tx prefix hash: ed535e91f7a313f1d0e270d321234e2d6440243049f19b9cb9e7eac8a710f893
Tx public key: 2716ab2be269a07b5b3d6141f5965ba31d00a2b872dd3a920b7e1acb20488a17
Timestamp: 1705622676 Timestamp [UCT]: 2024-01-19 00:04:36 Age [y:d:h:m:s]: 01:080:12:00:33
Block: 938339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318623 RingCT/type: yes/0
Extra: 012716ab2be269a07b5b3d6141f5965ba31d00a2b872dd3a920b7e1acb20488a170211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 730f342e0fddd8a5d6f3ac98d146ce4e94eb3d8a643d8f5bfaf54680b85efe68 0.600000000000 1396409 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": 938349, "vin": [ { "gen": { "height": 938339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "730f342e0fddd8a5d6f3ac98d146ce4e94eb3d8a643d8f5bfaf54680b85efe68" } } ], "extra": [ 1, 39, 22, 171, 43, 226, 105, 160, 123, 91, 61, 97, 65, 245, 150, 91, 163, 29, 0, 162, 184, 114, 221, 58, 146, 11, 126, 26, 203, 32, 72, 138, 23, 2, 17, 0, 0, 0, 5, 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