Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0795b03f8e85a7254c4883e49bb1f37eea0efff10f20610b5e91701598dcccd8

Tx prefix hash: 665f36728795f0b35fef0b876c6f3c0bd0466d904aee6012e028aa71f984b9a0
Tx public key: ee6be90bc94f8a6f2902bafca70dccd9ece1aa9122399235b193586b1be84bd4
Timestamp: 1775033289 Timestamp [UTC]: 2026-04-01 08:48:09 Age [y:d:h:m:s]: 00:232:05:12:26
Block: 1510400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171541 RingCT/type: yes/0
Extra: 01ee6be90bc94f8a6f2902bafca70dccd9ece1aa9122399235b193586b1be84bd4021100000005e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a6f5f25bf81f41c567e6aa40f7e6e3195118f2862c0d08406528bee068eb7d08 0.000600000000 2000184 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": 1510410, "vin": [ { "gen": { "height": 1510400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6f5f25bf81f41c567e6aa40f7e6e3195118f2862c0d08406528bee068eb7d08" } } ], "extra": [ 1, 238, 107, 233, 11, 201, 79, 138, 111, 41, 2, 186, 252, 167, 13, 204, 217, 236, 225, 170, 145, 34, 57, 146, 53, 177, 147, 88, 107, 27, 232, 75, 212, 2, 17, 0, 0, 0, 5, 227, 215, 220, 159, 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: