Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f60145bc617039afec68d3c22f9ca29fff88ed3cb480ffe30d5d08bf048bfc96

Tx prefix hash: 83753c2c683da441d64aac436a1b1fc2e6121ec12b7d3bc663b5f4df334d24a3
Tx public key: 07c47b3ec211316089a3165f94cc58688f5e16879dcc6a2a97022368c947b2e1
Timestamp: 1726968302 Timestamp [UCT]: 2024-09-22 01:25:02 Age [y:d:h:m:s]: 00:173:10:51:15
Block: 1115325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123796 RingCT/type: yes/0
Extra: 0107c47b3ec211316089a3165f94cc58688f5e16879dcc6a2a97022368c947b2e1021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66dec5ae5b4938afa6c9db6b83d4652d938a92d5ea52cd66cbcc5ceb092aec32 0.600000000000 1595420 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": 1115335, "vin": [ { "gen": { "height": 1115325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66dec5ae5b4938afa6c9db6b83d4652d938a92d5ea52cd66cbcc5ceb092aec32" } } ], "extra": [ 1, 7, 196, 123, 62, 194, 17, 49, 96, 137, 163, 22, 95, 148, 204, 88, 104, 143, 94, 22, 135, 157, 204, 106, 42, 151, 2, 35, 104, 201, 71, 178, 225, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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