Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ea186e2c2e7ff6c36c41a767b5e3e686afb8e73ef809b6731c5752f96dcdfd7

Tx prefix hash: 1bd3751cb2eb03c5e72a9841a51787b86cea04c849b17a58fbb8e231da71a47c
Tx public key: 39caed52f8812becf7e6318bb4acbd8752daf2a7ad54af6383a0b6504d60c6a3
Timestamp: 1745747120 Timestamp [UCT]: 2025-04-27 09:45:20 Age [y:d:h:m:s]: 00:242:22:26:09
Block: 1270505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171382 RingCT/type: yes/0
Extra: 0139caed52f8812becf7e6318bb4acbd8752daf2a7ad54af6383a0b6504d60c6a30211000000072609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1172c8df17171dc3ff02ee74eedd28cc9f112f6a19e31ce965378fcddd43781 0.600000000000 1757748 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": 1270515, "vin": [ { "gen": { "height": 1270505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1172c8df17171dc3ff02ee74eedd28cc9f112f6a19e31ce965378fcddd43781" } } ], "extra": [ 1, 57, 202, 237, 82, 248, 129, 43, 236, 247, 230, 49, 139, 180, 172, 189, 135, 82, 218, 242, 167, 173, 84, 175, 99, 131, 160, 182, 80, 77, 96, 198, 163, 2, 17, 0, 0, 0, 7, 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