Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae15dee193da4b72f2c85ac3a301868aab245f2c90244f07f59cbf175c3c4892

Tx prefix hash: f7c1316606ea68cf4a3aa24804e7900a04d0646ba2d79ad1bfff86e25aa59561
Tx public key: 01bd98ff9860674f8837fa1b3cb5ff51f18676e48310de5bc2ae40c0db868fb8
Timestamp: 1718527636 Timestamp [UCT]: 2024-06-16 08:47:16 Age [y:d:h:m:s]: 00:271:16:08:23
Block: 1045366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194130 RingCT/type: yes/0
Extra: 0101bd98ff9860674f8837fa1b3cb5ff51f18676e48310de5bc2ae40c0db868fb802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e4d3b26a7f2ac77c6dbc2804ef4e0e951e0c5863bf92506ea2d22bdd489d916 0.600000000000 1514915 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": 1045376, "vin": [ { "gen": { "height": 1045366 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e4d3b26a7f2ac77c6dbc2804ef4e0e951e0c5863bf92506ea2d22bdd489d916" } } ], "extra": [ 1, 1, 189, 152, 255, 152, 96, 103, 79, 136, 55, 250, 27, 60, 181, 255, 81, 241, 134, 118, 228, 131, 16, 222, 91, 194, 174, 64, 192, 219, 134, 143, 184, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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