Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c5f8a99aa1c16e8cdd4ca5a4d4bb8142f4a0f8eb48a21210960eb8cf2f107de

Tx prefix hash: b5a783680f512531c4024f9ea6ce60652a5b131102c7b054b2d9f5a99bacc695
Tx public key: de3df4dd891519e49889b95b21c5b57ffe1877a4ef0d88862c2d646fe84f6693
Timestamp: 1760758551 Timestamp [UTC]: 2025-10-18 03:35:51 Age [y:d:h:m:s]: 01:033:08:53:59
Block: 1392361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290318 RingCT/type: yes/0
Extra: 01de3df4dd891519e49889b95b21c5b57ffe1877a4ef0d88862c2d646fe84f66930211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 461e83b190321b9badb776bab1616dae9a691f2cfb980f7041de6d208c856ed0 0.000600000000 1880612 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": 1392371, "vin": [ { "gen": { "height": 1392361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "461e83b190321b9badb776bab1616dae9a691f2cfb980f7041de6d208c856ed0" } } ], "extra": [ 1, 222, 61, 244, 221, 137, 21, 25, 228, 152, 137, 185, 91, 33, 197, 181, 127, 254, 24, 119, 164, 239, 13, 136, 134, 44, 45, 100, 111, 232, 79, 102, 147, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: