Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dc2ba68124bf788b0d6abbb771332b0ee906a8b22ecd69e3a2264b87befd456

Tx prefix hash: 81297e111f4a4f7902547ca832095d395a295760cbcc324515f5120f8af36df8
Tx public key: ec4b1eeb4677b15cc63100ae2ef84d35243b9ee513e0e66c5969800de3a5bd41
Timestamp: 1741770806 Timestamp [UTC]: 2025-03-12 09:13:26 Age [y:d:h:m:s]: 01:063:08:29:46
Block: 1237592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296169 RingCT/type: yes/0
Extra: 01ec4b1eeb4677b15cc63100ae2ef84d35243b9ee513e0e66c5969800de3a5bd410211000000031f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b271d41f9c3947e84581275720cac5a997b1137fe97dd62612a1f9f2cf1a16c9 0.000600000000 1724547 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": 1237602, "vin": [ { "gen": { "height": 1237592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b271d41f9c3947e84581275720cac5a997b1137fe97dd62612a1f9f2cf1a16c9" } } ], "extra": [ 1, 236, 75, 30, 235, 70, 119, 177, 92, 198, 49, 0, 174, 46, 248, 77, 53, 36, 59, 158, 229, 19, 224, 230, 108, 89, 105, 128, 13, 227, 165, 189, 65, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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: