Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a9d10234d1f2bb58fa039be3bd5eaeca4eca428cd5d9f0c6327de443da0658f

Tx prefix hash: ddc9e21c60c911738be048d6ead4f1293a5452858e5afb68874b3fad6765d9ec
Tx public key: c25b044fc8c4a605b32a7d97fec0c5aa67ff62ace238423cbccae156ed270960
Timestamp: 1771258396 Timestamp [UTC]: 2026-02-16 16:13:16 Age [y:d:h:m:s]: 00:273:14:46:17
Block: 1479153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201061 RingCT/type: yes/0
Extra: 01c25b044fc8c4a605b32a7d97fec0c5aa67ff62ace238423cbccae156ed270960021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c07c76c8ccb2dd8e717266bc1384fa6b204db171b0a3dc7a1611b6d04176a252 0.000600000000 1968487 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": 1479163, "vin": [ { "gen": { "height": 1479153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c07c76c8ccb2dd8e717266bc1384fa6b204db171b0a3dc7a1611b6d04176a252" } } ], "extra": [ 1, 194, 91, 4, 79, 200, 196, 166, 5, 179, 42, 125, 151, 254, 192, 197, 170, 103, 255, 98, 172, 226, 56, 66, 60, 188, 202, 225, 86, 237, 39, 9, 96, 2, 17, 0, 0, 0, 4, 228, 245, 25, 63, 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: