Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6870c2e96d21bd449a0108c33104483c6d9c1c7d56f5ac07ca96e7a17e40bb5a

Tx prefix hash: bf9427884453297fa0d97c542027f674019809a1f2edec98f542d96bebbc0b32
Tx public key: bf5bfb3664759ed477b645138b415388cacd79a170cd94e2ddae30e4865a0a6a
Timestamp: 1771416188 Timestamp [UTC]: 2026-02-18 12:03:08 Age [y:d:h:m:s]: 00:275:16:25:39
Block: 1480456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202707 RingCT/type: yes/0
Extra: 01bf5bfb3664759ed477b645138b415388cacd79a170cd94e2ddae30e4865a0a6a021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3c02dc364e6df82487d35d9ba33623aa2a55264e257729e954a1ecfdd8d28e3a 0.000600000000 1969826 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": 1480466, "vin": [ { "gen": { "height": 1480456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c02dc364e6df82487d35d9ba33623aa2a55264e257729e954a1ecfdd8d28e3a" } } ], "extra": [ 1, 191, 91, 251, 54, 100, 117, 158, 212, 119, 182, 69, 19, 139, 65, 83, 136, 202, 205, 121, 161, 112, 205, 148, 226, 221, 174, 48, 228, 134, 90, 10, 106, 2, 17, 0, 0, 0, 3, 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: