Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22150158608d311495c011b576bae5b2517874948abe368a5a9af039763c3325

Tx prefix hash: c73923fba29d5f43b21f4ffe3d20ab90ff0577c6a5f8d91d7161f0e5068eeb7a
Tx public key: 8ffbac2e4f7402ac2a8fe6373edb40446b6a74014ab3ea43e88b432d8c28f04f
Timestamp: 1760545413 Timestamp [UCT]: 2025-10-15 16:23:33 Age [y:d:h:m:s]: 00:042:17:56:33
Block: 1390583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30606 RingCT/type: yes/0
Extra: 018ffbac2e4f7402ac2a8fe6373edb40446b6a74014ab3ea43e88b432d8c28f04f0211000000052609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8affdabe615ae406f8855a00f81ce41148fd457a3c8cb856a0eb5fb5b7eef4c7 0.600000000000 1878830 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": 1390593, "vin": [ { "gen": { "height": 1390583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8affdabe615ae406f8855a00f81ce41148fd457a3c8cb856a0eb5fb5b7eef4c7" } } ], "extra": [ 1, 143, 251, 172, 46, 79, 116, 2, 172, 42, 143, 230, 55, 62, 219, 64, 68, 107, 106, 116, 1, 74, 179, 234, 67, 232, 139, 67, 45, 140, 40, 240, 79, 2, 17, 0, 0, 0, 5, 38, 9, 179, 160, 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