Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e57fc53011a7eb4fab12babde0cb11e522e50f59487c9729533e1a6df10c5de

Tx prefix hash: 01468edaa7e8ced898572bc20e8f31bd37b5ae1f2bdfaf9b42f6862b6f77e81c
Tx public key: c13cb853c7f9db2a338253ed5dd36f20e8a539c2adfec01f9bdad3380b63281d
Timestamp: 1770075916 Timestamp [UTC]: 2026-02-02 23:45:16 Age [y:d:h:m:s]: 00:289:14:01:02
Block: 1469387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212545 RingCT/type: yes/0
Extra: 01c13cb853c7f9db2a338253ed5dd36f20e8a539c2adfec01f9bdad3380b63281d021100000008e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cab63f1b9808dc8207c86c74fca2f3c5d9c6645e239579aacc802bb42180c407 0.000600000000 1958645 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": 1469397, "vin": [ { "gen": { "height": 1469387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cab63f1b9808dc8207c86c74fca2f3c5d9c6645e239579aacc802bb42180c407" } } ], "extra": [ 1, 193, 60, 184, 83, 199, 249, 219, 42, 51, 130, 83, 237, 93, 211, 111, 32, 232, 165, 57, 194, 173, 254, 192, 31, 155, 218, 211, 56, 11, 99, 40, 29, 2, 17, 0, 0, 0, 8, 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: