Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d9c3db2532f1e014e550866b94b805fb64703bb5cd29cea2bfff9353e26963f

Tx prefix hash: 24a1a07b8d2a8c1fe7e48c26f5dbea2405fe1c9857e7b443ae281bd537dbfea2
Tx public key: 5235a0a1d4fddef80f5f68253428bc75f12e4e95252f5c137302abb2c3de56a5
Timestamp: 1751655463 Timestamp [UCT]: 2025-07-04 18:57:43 Age [y:d:h:m:s]: 00:138:13:03:46
Block: 1318770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97336 RingCT/type: yes/0
Extra: 015235a0a1d4fddef80f5f68253428bc75f12e4e95252f5c137302abb2c3de56a502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95e79867219d10367a43ceee5ba18a8247332cbe6d226a6496f04a26b03e8931 0.600000000000 1806457 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": 1318780, "vin": [ { "gen": { "height": 1318770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95e79867219d10367a43ceee5ba18a8247332cbe6d226a6496f04a26b03e8931" } } ], "extra": [ 1, 82, 53, 160, 161, 212, 253, 222, 248, 15, 95, 104, 37, 52, 40, 188, 117, 241, 46, 78, 149, 37, 47, 92, 19, 115, 2, 171, 178, 195, 222, 86, 165, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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