Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08142ee14e9d1593d567afcc5d40c0e9ffece1b03debaaff0720db70ebdd0669

Tx prefix hash: 4f717a196d097c78ca33064d945736478d835464acc3c43421c11aa5e856b698
Tx public key: dd25e648c7b8fa2ce9320661dee910cdd2550b2d38ad2956745cb3caeb0b2aee
Timestamp: 1763947079 Timestamp [UTC]: 2025-11-24 01:17:59 Age [y:d:h:m:s]: 00:359:07:27:36
Block: 1418769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262244 RingCT/type: yes/0
Extra: 01dd25e648c7b8fa2ce9320661dee910cdd2550b2d38ad2956745cb3caeb0b2aee0211000000038ceb7f09000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 916acf55860e3e3acb25d8d91f6cec186f1964bce4edb3d8c4d18a107f4534f4 0.000600000000 1907302 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": 1418779, "vin": [ { "gen": { "height": 1418769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "916acf55860e3e3acb25d8d91f6cec186f1964bce4edb3d8c4d18a107f4534f4" } } ], "extra": [ 1, 221, 37, 230, 72, 199, 184, 250, 44, 233, 50, 6, 97, 222, 233, 16, 205, 210, 85, 11, 45, 56, 173, 41, 86, 116, 92, 179, 202, 235, 11, 42, 238, 2, 17, 0, 0, 0, 3, 140, 235, 127, 9, 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: