Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaa93a200cb3a63f9545e84d54b5aad69b982bbb46a5c835f44e6239d3693cd6

Tx prefix hash: 0db3681e056e37f59b3e56cb9c1fb7a272f970413dfab464ced2cc3d5d96881f
Tx public key: 5b89df2b5d3d7880d9659d6925d437e15710950b1443cee524c3dc4fd9b7b962
Timestamp: 1757512552 Timestamp [UTC]: 2025-09-10 13:55:52 Age [y:d:h:m:s]: 01:072:06:22:15
Block: 1365447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318047 RingCT/type: yes/0
Extra: 015b89df2b5d3d7880d9659d6925d437e15710950b1443cee524c3dc4fd9b7b962021100000001ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5ba8722f848a2e60c6d3284374c1ddb1dbedc27ab2694ceddc091376c2627343 0.000600000000 1853486 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": 1365457, "vin": [ { "gen": { "height": 1365447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ba8722f848a2e60c6d3284374c1ddb1dbedc27ab2694ceddc091376c2627343" } } ], "extra": [ 1, 91, 137, 223, 43, 93, 61, 120, 128, 217, 101, 157, 105, 37, 212, 55, 225, 87, 16, 149, 11, 20, 67, 206, 229, 36, 195, 220, 79, 217, 183, 185, 98, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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: