Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d595c9a1909d9f6eb652292e105a00669e273443ccdbcabd0e70cf6efe5aa8a

Tx prefix hash: f132873d52a1a9bc558e46717bf8cbc9ba64f8c4da6b166706b112501dfa932f
Tx public key: 80d9502ff0c362ec4a4bcebf1741f7fec886164d9de8516cba42496eec15bec2
Timestamp: 1768312644 Timestamp [UTC]: 2026-01-13 13:57:24 Age [y:d:h:m:s]: 00:309:20:38:38
Block: 1454807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227016 RingCT/type: yes/0
Extra: 0180d9502ff0c362ec4a4bcebf1741f7fec886164d9de8516cba42496eec15bec2021100000001215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 89d8e6a79e4e7d8621d407157bc776073cda2b3a3da633930388ba418fe7d3b5 0.000600000000 1943899 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": 1454817, "vin": [ { "gen": { "height": 1454807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89d8e6a79e4e7d8621d407157bc776073cda2b3a3da633930388ba418fe7d3b5" } } ], "extra": [ 1, 128, 217, 80, 47, 240, 195, 98, 236, 74, 75, 206, 191, 23, 65, 247, 254, 200, 134, 22, 77, 157, 232, 81, 108, 186, 66, 73, 110, 236, 21, 190, 194, 2, 17, 0, 0, 0, 1, 33, 91, 191, 137, 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: