Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f90213592c7cce30aabe09f296fdd43b6cff46fbade9f956147d4feec8d601ef

Tx prefix hash: bb046d5d3825a789260bb224ceeea639c4865474dcd572f6612d5c37377580f5
Tx public key: dcef5ff64eff9956a9e8e3943e1ae4c917b2877ae26314333712252764e8300b
Timestamp: 1710447928 Timestamp [UCT]: 2024-03-14 20:25:28 Age [y:d:h:m:s]: 01:042:18:09:16
Block: 978381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291551 RingCT/type: yes/0
Extra: 01dcef5ff64eff9956a9e8e3943e1ae4c917b2877ae26314333712252764e8300b0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600050000000 dcy

stealth address amount amount idx
00: 420c7214397d9aef8cbff28532aa18ed70e7fd3dc9d9d9a93db41cd6523c7c4e 0.600050000000 1438406 of 0

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": 978391, "vin": [ { "gen": { "height": 978381 } } ], "vout": [ { "amount": 600050000, "target": { "key": "420c7214397d9aef8cbff28532aa18ed70e7fd3dc9d9d9a93db41cd6523c7c4e" } } ], "extra": [ 1, 220, 239, 95, 246, 78, 255, 153, 86, 169, 232, 227, 148, 62, 26, 228, 201, 23, 178, 135, 122, 226, 99, 20, 51, 55, 18, 37, 39, 100, 232, 48, 11, 2, 17, 0, 0, 0, 6, 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