Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2aa18656514c8ba2087b5d8afa33622b2af5c82e70122d80fc2d0ba10276da4b

Tx prefix hash: 2cd5184d1333c74e363a11a2502b257855a9b7438d14e4326ea54cd033cdaaec
Tx public key: 5974623fd9b6a19f0eaaec644947d1773f00e209f8b37db54192795372e87507
Timestamp: 1749291900 Timestamp [UCT]: 2025-06-07 10:25:00 Age [y:d:h:m:s]: 00:156:11:09:22
Block: 1299854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109497 RingCT/type: yes/0
Extra: 015974623fd9b6a19f0eaaec644947d1773f00e209f8b37db54192795372e87507021100000008bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b0650509f427d8c90a4d0a261967a7d45aa1e22919eede228cbc0a7ada9c261 0.600000000000 1787395 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": 1299864, "vin": [ { "gen": { "height": 1299854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b0650509f427d8c90a4d0a261967a7d45aa1e22919eede228cbc0a7ada9c261" } } ], "extra": [ 1, 89, 116, 98, 63, 217, 182, 161, 159, 14, 170, 236, 100, 73, 71, 209, 119, 63, 0, 226, 9, 248, 179, 125, 181, 65, 146, 121, 83, 114, 232, 117, 7, 2, 17, 0, 0, 0, 8, 191, 81, 178, 162, 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