Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ae100c6f5f660414829d702f4523a79168bceb52fd572f5185d3288d823fa10

Tx prefix hash: 02ac17cf9f2882417b62595eaea7236590c585d02f5f432305b7bfd45c987fe2
Tx public key: 94e9148e962b0ef8cad6ea2a2c7c32d91ae2febc0ba751e17f87ed290503f79c
Timestamp: 1746172208 Timestamp [UCT]: 2025-05-02 07:50:08 Age [y:d:h:m:s]: 00:203:07:13:18
Block: 1274017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143003 RingCT/type: yes/0
Extra: 0194e9148e962b0ef8cad6ea2a2c7c32d91ae2febc0ba751e17f87ed290503f79c0211000000069f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd1094c30613972620522911bc656b4ae51b2ffef342f27d8b7f3ba32cb71438 0.600000000000 1761306 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": 1274027, "vin": [ { "gen": { "height": 1274017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd1094c30613972620522911bc656b4ae51b2ffef342f27d8b7f3ba32cb71438" } } ], "extra": [ 1, 148, 233, 20, 142, 150, 43, 14, 248, 202, 214, 234, 42, 44, 124, 50, 217, 26, 226, 254, 188, 11, 167, 81, 225, 127, 135, 237, 41, 5, 3, 247, 156, 2, 17, 0, 0, 0, 6, 159, 159, 230, 140, 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