Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 797dc7969ff9a085c5e7b6312cd86e6e0f7cee410a9baa7852e3b59fe71a8b7c

Tx prefix hash: 8cfe74898cc6bce1177ce52d1873b8d387a01bf3ae8d9f625532d117ced2d071
Tx public key: cc9f71175eeaf68418a8b91e3e4c385bc3689f3af49b0b9fd1d88f3c88069d56
Timestamp: 1745127995 Timestamp [UTC]: 2025-04-20 05:46:35 Age [y:d:h:m:s]: 01:216:00:44:26
Block: 1265355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418139 RingCT/type: yes/0
Extra: 01cc9f71175eeaf68418a8b91e3e4c385bc3689f3af49b0b9fd1d88f3c88069d56021100000005dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 61e5ec3576cbb9ba7a727c1a86f7af12b285e9cde75308983566db7070a346d3 0.000600000000 1752562 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": 1265365, "vin": [ { "gen": { "height": 1265355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61e5ec3576cbb9ba7a727c1a86f7af12b285e9cde75308983566db7070a346d3" } } ], "extra": [ 1, 204, 159, 113, 23, 94, 234, 246, 132, 24, 168, 185, 30, 62, 76, 56, 91, 195, 104, 159, 58, 244, 155, 11, 159, 209, 216, 143, 60, 136, 6, 157, 86, 2, 17, 0, 0, 0, 5, 219, 181, 113, 193, 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: