Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68571ce7ef64507053ea4080b2774689ded55dacbf6c69c4e2ac7a082be19b0c

Tx prefix hash: 7a427b53d007598918d623a01ee7c1c1d583929b54c928161099b928b10f1286
Tx public key: fbeb8445881a37af4a59037957f599a91b9ce3666f418d21a4d6e67d02a021a8
Timestamp: 1726137296 Timestamp [UCT]: 2024-09-12 10:34:56 Age [y:d:h:m:s]: 00:208:22:57:20
Block: 1108431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149181 RingCT/type: yes/0
Extra: 01fbeb8445881a37af4a59037957f599a91b9ce3666f418d21a4d6e67d02a021a8021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efb074b243715dca0d06cc12422120ae0ae09275b28948588b7608866fd5a5c6 0.600000000000 1586322 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": 1108441, "vin": [ { "gen": { "height": 1108431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efb074b243715dca0d06cc12422120ae0ae09275b28948588b7608866fd5a5c6" } } ], "extra": [ 1, 251, 235, 132, 69, 136, 26, 55, 175, 74, 89, 3, 121, 87, 245, 153, 169, 27, 156, 227, 102, 111, 65, 141, 33, 164, 214, 230, 125, 2, 160, 33, 168, 2, 17, 0, 0, 0, 6, 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