Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f8647f44ac0cf794fe71b68cdf2cc725c524aaef98bdf60b1e9234a5e9243be

Tx prefix hash: 129a3d9686a8bcdd23a0e18075e5b0d3adf5854bab58b9ca81bf09288a18216b
Tx public key: f7924cd9c99d9c830afddc05fa82677d8bf415e1bf3a446f6fcef5e000c1549f
Timestamp: 1743328617 Timestamp [UCT]: 2025-03-30 09:56:57 Age [y:d:h:m:s]: 00:279:00:25:08
Block: 1250470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197222 RingCT/type: yes/0
Extra: 01f7924cd9c99d9c830afddc05fa82677d8bf415e1bf3a446f6fcef5e000c1549f0211000000081a970403000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: daf21f1c6ad694de25f1a6e2bb806dc2cb3a9620657b54c5693b505b49b0566e 0.600000000000 1737519 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": 1250480, "vin": [ { "gen": { "height": 1250470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "daf21f1c6ad694de25f1a6e2bb806dc2cb3a9620657b54c5693b505b49b0566e" } } ], "extra": [ 1, 247, 146, 76, 217, 201, 157, 156, 131, 10, 253, 220, 5, 250, 130, 103, 125, 139, 244, 21, 225, 191, 58, 68, 111, 111, 206, 245, 224, 0, 193, 84, 159, 2, 17, 0, 0, 0, 8, 26, 151, 4, 3, 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