Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2d01fc93f549ca25ed99ebb0cb83991e7861fe469d4c40ed0255e041ab5b88d

Tx prefix hash: 74f3fe346e753d180b377bee31297603fbf5d307a1e81468cda46f4fc9aad0de
Tx public key: f376b1f815312e3922ced125a5c85e42caee579b53e9cc079aca120b5da002c3
Timestamp: 1767975607 Timestamp [UTC]: 2026-01-09 16:20:07 Age [y:d:h:m:s]: 00:317:03:12:48
Block: 1452159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231991 RingCT/type: yes/0
Extra: 01f376b1f815312e3922ced125a5c85e42caee579b53e9cc079aca120b5da002c3021100000018215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 14ef226ee78e23ef731e7e5a2618c5512b1159e17297d5d6b37f75f0bd6d5e3d 0.000600000000 1941179 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": 1452169, "vin": [ { "gen": { "height": 1452159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14ef226ee78e23ef731e7e5a2618c5512b1159e17297d5d6b37f75f0bd6d5e3d" } } ], "extra": [ 1, 243, 118, 177, 248, 21, 49, 46, 57, 34, 206, 209, 37, 165, 200, 94, 66, 202, 238, 87, 155, 83, 233, 204, 7, 154, 202, 18, 11, 93, 160, 2, 195, 2, 17, 0, 0, 0, 24, 33, 91, 191, 137, 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: