Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b02595a871f3bf8a29b6861c2aa5fe42a27570d4e0393fbd1360ffebac8cdda

Tx prefix hash: 14cd30dcd8027eaa02bbaeaf8a3d6727f1b5b8c97107cb232c740936686e7ca8
Tx public key: 4d2527d5465f73e0d04d83a007e85ed20797171d0169bc00c72dd4e555100cc8
Timestamp: 1738770095 Timestamp [UTC]: 2025-02-05 15:41:35 Age [y:d:h:m:s]: 01:006:19:49:14
Block: 1212737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263363 RingCT/type: yes/0
Extra: 014d2527d5465f73e0d04d83a007e85ed20797171d0169bc00c72dd4e555100cc80211000000031f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 96627cbb045bc7cb10723ab98b78562b5c5e9d894159c99e0840b2e818aa89e6 0.000600000000 1699510 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": 1212747, "vin": [ { "gen": { "height": 1212737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96627cbb045bc7cb10723ab98b78562b5c5e9d894159c99e0840b2e818aa89e6" } } ], "extra": [ 1, 77, 37, 39, 213, 70, 95, 115, 224, 208, 77, 131, 160, 7, 232, 94, 210, 7, 151, 23, 29, 1, 105, 188, 0, 199, 45, 212, 229, 85, 16, 12, 200, 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) | dinastycoin version: tesla-369