Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e82f342e342b3bb0de8e02d5817a0027666d476491c94d481af05d1463684887

Tx prefix hash: 8ab0d6b10f679137d0a0159c56d8d2ff50c31f8cb7e9cb0e543bc237a5bfe212
Tx public key: 664113a49a7d1260832aed2a8426e1e7110f7a9b0ecfa12ceb3ec6ed6f3c30d3
Timestamp: 1753639192 Timestamp [UCT]: 2025-07-27 17:59:52 Age [y:d:h:m:s]: 00:025:00:38:29
Block: 1334664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16784 RingCT/type: yes/0
Extra: 01664113a49a7d1260832aed2a8426e1e7110f7a9b0ecfa12ceb3ec6ed6f3c30d302110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa966596f79e97675b5f994df1ae6e42918ef4df50c79ab1936bc321d7459804 0.600000000000 1822465 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": 1334674, "vin": [ { "gen": { "height": 1334664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa966596f79e97675b5f994df1ae6e42918ef4df50c79ab1936bc321d7459804" } } ], "extra": [ 1, 102, 65, 19, 164, 154, 125, 18, 96, 131, 42, 237, 42, 132, 38, 225, 231, 17, 15, 122, 155, 14, 207, 161, 44, 235, 62, 198, 237, 111, 60, 48, 211, 2, 17, 0, 0, 0, 2, 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