Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c86934d04a56f7ca56d775493516c469f2b9aeb599097f57781c486fae53e005

Tx prefix hash: 1f46761dedb92b2141fab2ba23b14877b67d3d8bf3723a0eff2c2fb80eabbca2
Tx public key: a3d70e8c867a9e0ee28074cf13b25e4ff0eeb55344767418eab862c35720c336
Timestamp: 1760712712 Timestamp [UTC]: 2025-10-17 14:51:52 Age [y:d:h:m:s]: 01:032:20:55:31
Block: 1391978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289882 RingCT/type: yes/0
Extra: 01a3d70e8c867a9e0ee28074cf13b25e4ff0eeb55344767418eab862c35720c336021100000001df5a247a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c9c22e81aaa576563e9d0fb6e736aff9d94c3ce04ce2551a168e0831b4ae7295 0.000600000000 1880227 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": 1391988, "vin": [ { "gen": { "height": 1391978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9c22e81aaa576563e9d0fb6e736aff9d94c3ce04ce2551a168e0831b4ae7295" } } ], "extra": [ 1, 163, 215, 14, 140, 134, 122, 158, 14, 226, 128, 116, 207, 19, 178, 94, 79, 240, 238, 181, 83, 68, 118, 116, 24, 234, 184, 98, 195, 87, 32, 195, 54, 2, 17, 0, 0, 0, 1, 223, 90, 36, 122, 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: