Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1f1c7e31df6fc1ab7df8420f701260cd683fa197a0b4dae5e4aa4e9fb446819

Tx prefix hash: df85185a2486ab1a97602defd9e40c4d5a6d701d4dd9674cc10ddbb47c1911d5
Tx public key: 1020aff73a6dfc05a8fe2039044ad59abf6c35e0a535d8f2c4c5c98736c54a02
Timestamp: 1774186298 Timestamp [UTC]: 2026-03-22 13:31:38 Age [y:d:h:m:s]: 00:238:16:18:44
Block: 1503375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176064 RingCT/type: yes/0
Extra: 011020aff73a6dfc05a8fe2039044ad59abf6c35e0a535d8f2c4c5c98736c54a02021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 80f78f9dc59dc154131b92b8cd00123574bd9a50bddb3a5e5de6085a41f00110 0.000600000000 1993083 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": 1503385, "vin": [ { "gen": { "height": 1503375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80f78f9dc59dc154131b92b8cd00123574bd9a50bddb3a5e5de6085a41f00110" } } ], "extra": [ 1, 16, 32, 175, 247, 58, 109, 252, 5, 168, 254, 32, 57, 4, 74, 213, 154, 191, 108, 53, 224, 165, 53, 216, 242, 196, 197, 201, 135, 54, 197, 74, 2, 2, 17, 0, 0, 0, 6, 241, 136, 200, 168, 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: