Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f0ef3469719a4d965f2a78bcb39cda1989bd0c02cd6860cb3e76c011f30ef4d

Tx prefix hash: a00325ccd4966b872d8ec49da60f8c95f3ccf0a5ff1cd2656a32945f4d770ff2
Tx public key: bb6811463193a660c57a144919dfd3bbdbd08ff0b10f19d3a781a739c2d2de40
Timestamp: 1728426080 Timestamp [UCT]: 2024-10-08 22:21:20 Age [y:d:h:m:s]: 00:007:22:34:38
Block: 1127406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5695 RingCT/type: yes/0
Extra: 01bb6811463193a660c57a144919dfd3bbdbd08ff0b10f19d3a781a739c2d2de4002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bee82dba9f7462296db9a928bf8ccb2b20a3fb4377222785ece6d9edb51b426f 0.600000000000 1610211 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": 1127416, "vin": [ { "gen": { "height": 1127406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bee82dba9f7462296db9a928bf8ccb2b20a3fb4377222785ece6d9edb51b426f" } } ], "extra": [ 1, 187, 104, 17, 70, 49, 147, 166, 96, 197, 122, 20, 73, 25, 223, 211, 187, 219, 208, 143, 240, 177, 15, 25, 211, 167, 129, 167, 57, 194, 210, 222, 64, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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