Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 412053c404f0af817c1307fc0dc499fa0a5292973e97be51e6bbf6bb095489f3

Tx prefix hash: 98f597e08b8173c21097d60f2845480671041058efbd4d87dded2504f586f61e
Tx public key: 69b2ea07cc5df1d20d3d34248fa10ae0a7ed83ce9829b2f7d3033c94785c2000
Timestamp: 1772394865 Timestamp [UTC]: 2026-03-01 19:54:25 Age [y:d:h:m:s]: 00:264:13:01:38
Block: 1488569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194731 RingCT/type: yes/0
Extra: 0169b2ea07cc5df1d20d3d34248fa10ae0a7ed83ce9829b2f7d3033c94785c2000021100000008e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0af7a2234d7f7097cfcdd157848eb959739f5bde630acfbcb566427731a33350 0.000600000000 1978049 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 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": 1488579, "vin": [ { "gen": { "height": 1488569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0af7a2234d7f7097cfcdd157848eb959739f5bde630acfbcb566427731a33350" } } ], "extra": [ 1, 105, 178, 234, 7, 204, 93, 241, 210, 13, 61, 52, 36, 143, 161, 10, 224, 167, 237, 131, 206, 152, 41, 178, 247, 211, 3, 60, 148, 120, 92, 32, 0, 2, 17, 0, 0, 0, 8, 228, 245, 25, 63, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


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