Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f58634ba6ca65c300c4038e0ded7d0f497d6cfd26865cc74ee4100d6788c93d

Tx prefix hash: 471be548c712d3d65595d80b7923468ca23d9a055afd53b90dc579510923de3b
Tx public key: 3edcec97c89f7c6a3984fe40116901ed83085f51e4eda027334048b6c928e891
Timestamp: 1782254813 Timestamp [UTC]: 2026-06-23 22:46:53 Age [y:d:h:m:s]: 00:151:21:26:05
Block: 1566511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 117639 RingCT/type: yes/0
Extra: 013edcec97c89f7c6a3984fe40116901ed83085f51e4eda027334048b6c928e8910208c338d35f90902c1e

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a46436b12fbf0bb427b8367599d68e2d521fa5d5aef704f610b9783205bddf3a 0.000600000000 2056491 of 15 <95>

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 dinastycoin-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": 1566521, "vin": [ { "gen": { "height": 1566511 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "a46436b12fbf0bb427b8367599d68e2d521fa5d5aef704f610b9783205bddf3a", "view_tag": "95" } } } ], "extra": [ 1, 62, 220, 236, 151, 200, 159, 124, 106, 57, 132, 254, 64, 17, 105, 1, 237, 131, 8, 95, 81, 228, 237, 160, 39, 51, 64, 72, 182, 201, 40, 232, 145, 2, 8, 195, 56, 211, 95, 144, 144, 44, 30 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: