Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3042d5147be21e31adf5c0fcb25ef95df010ec9ebb10fba1567bba10cc14d380

Tx prefix hash: ae539f438976f5582705fb9d240654303a71b772e4d54ac52bd702699a1b26c9
Tx public key: 0ce5a6c4fa593227ff5255f6c45298d25e28e654435e61ea4f16613893f5d36f
Timestamp: 1773213960 Timestamp [UTC]: 2026-03-11 07:26:00 Age [y:d:h:m:s]: 00:251:03:46:49
Block: 1495344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184993 RingCT/type: yes/0
Extra: 010ce5a6c4fa593227ff5255f6c45298d25e28e654435e61ea4f16613893f5d36f021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8d715373b480138c6e17568cc470f3b47350244e5a85e99e9849718e32cc4784 0.000600000000 1984954 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": 1495354, "vin": [ { "gen": { "height": 1495344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d715373b480138c6e17568cc470f3b47350244e5a85e99e9849718e32cc4784" } } ], "extra": [ 1, 12, 229, 166, 196, 250, 89, 50, 39, 255, 82, 85, 246, 196, 82, 152, 210, 94, 40, 230, 84, 67, 94, 97, 234, 79, 22, 97, 56, 147, 245, 211, 111, 2, 17, 0, 0, 0, 4, 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: