Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23c9db56227112733bd1ee3e6215c18cdba3ab3381275ca8edcdd8b7dab6037c

Tx prefix hash: 2482da95e6d5380ee80545cbe7f32c83775a3f1b3d3025ccb4f15eb5cc037ab2
Tx public key: 6dc3e79495b5d86f6516df4943b0f8bdcaa4b820db8017d6dd0514b283eb62b2
Timestamp: 1749656005 Timestamp [UCT]: 2025-06-11 15:33:25 Age [y:d:h:m:s]: 00:151:15:58:32
Block: 1302856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106080 RingCT/type: yes/0
Extra: 016dc3e79495b5d86f6516df4943b0f8bdcaa4b820db8017d6dd0514b283eb62b2021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8977516e81a9279c12896ad4946e9cb027128e0b74eebbcc6c0cf4667848c3e 0.600000000000 1790429 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": 1302866, "vin": [ { "gen": { "height": 1302856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8977516e81a9279c12896ad4946e9cb027128e0b74eebbcc6c0cf4667848c3e" } } ], "extra": [ 1, 109, 195, 231, 148, 149, 181, 216, 111, 101, 22, 223, 73, 67, 176, 248, 189, 202, 164, 184, 32, 219, 128, 23, 214, 221, 5, 20, 178, 131, 235, 98, 178, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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