Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2598fd4f6ca6bcacb2d801a2bc117c44f18aecfc9dfc66240cb146602272c9e0

Tx prefix hash: 91b53e026e8bfa143286d09c8f9a18333fa2a333b07f1c6fbf9ef866124dc043
Tx public key: ab33ed28e245c0ba142e19fc14ab099a6ce0c0289706804743a702bfe6426fa5
Timestamp: 1752499451 Timestamp [UCT]: 2025-07-14 13:24:11 Age [y:d:h:m:s]: 00:174:02:36:55
Block: 1325340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123241 RingCT/type: yes/0
Extra: 01ab33ed28e245c0ba142e19fc14ab099a6ce0c0289706804743a702bfe6426fa5021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b1b3954ee9ba1531d7d7e3263e839191e8fbc1c2a75402a418e5b26dcecfdf8 0.600000000000 1813085 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": 1325350, "vin": [ { "gen": { "height": 1325340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b1b3954ee9ba1531d7d7e3263e839191e8fbc1c2a75402a418e5b26dcecfdf8" } } ], "extra": [ 1, 171, 51, 237, 40, 226, 69, 192, 186, 20, 46, 25, 252, 20, 171, 9, 154, 108, 224, 192, 40, 151, 6, 128, 71, 67, 167, 2, 191, 230, 66, 111, 165, 2, 17, 0, 0, 0, 6, 191, 81, 178, 162, 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