Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86eb1ee3a2bd2c5b31fb48c6fc16d5075f847b6ffba4d5187b84de15cf307772

Tx prefix hash: 6d72b8e8322bfacccdc6a6a27879027848845df3c122a23bf49a1a649640911f
Tx public key: e7a6072c84106c45487a881d4d1778013716b485b52df0bab6cf5d3834e1f09d
Timestamp: 1744131301 Timestamp [UCT]: 2025-04-08 16:55:01 Age [y:d:h:m:s]: 00:173:02:09:26
Block: 1257114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121364 RingCT/type: yes/0
Extra: 01e7a6072c84106c45487a881d4d1778013716b485b52df0bab6cf5d3834e1f09d0211000000076c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ec8892977b71c6f02a6e6b4db1d26588917ca5a1f3e83414d335dcacd9dc147 0.600000000000 1744233 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": 1257124, "vin": [ { "gen": { "height": 1257114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ec8892977b71c6f02a6e6b4db1d26588917ca5a1f3e83414d335dcacd9dc147" } } ], "extra": [ 1, 231, 166, 7, 44, 132, 16, 108, 69, 72, 122, 136, 29, 77, 23, 120, 1, 55, 22, 180, 133, 181, 45, 240, 186, 182, 207, 93, 56, 52, 225, 240, 157, 2, 17, 0, 0, 0, 7, 108, 152, 170, 61, 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