Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01517f660d5d14f9dbdec41fa9589dc971a301536eb7194602e5bfd1be80a704

Tx prefix hash: ddddf7ca8f8380bba546caccaedf39f720c79a9c0882c5c6ac65468c68807a7e
Tx public key: 338a0daa3374bdec07e3e53f71828616f8050eb76b76f56868b9ac11bbf5fb2b
Timestamp: 1771948117 Timestamp [UTC]: 2026-02-24 15:48:37 Age [y:d:h:m:s]: 00:266:15:11:57
Block: 1484884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196073 RingCT/type: yes/0
Extra: 01338a0daa3374bdec07e3e53f71828616f8050eb76b76f56868b9ac11bbf5fb2b021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cb407a7642391859fc5431eb639228e40d94e12ad81325e93bbd6a35e170e242 0.000600000000 1974316 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": 1484894, "vin": [ { "gen": { "height": 1484884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb407a7642391859fc5431eb639228e40d94e12ad81325e93bbd6a35e170e242" } } ], "extra": [ 1, 51, 138, 13, 170, 51, 116, 189, 236, 7, 227, 229, 63, 113, 130, 134, 22, 248, 5, 14, 183, 107, 118, 245, 104, 104, 185, 172, 17, 187, 245, 251, 43, 2, 17, 0, 0, 0, 4, 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: