Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 874616dd8d60c3bbf1d38ed6d11780fc1ef0f7ef542b71bc4410c97ce5b8199f

Tx prefix hash: e6bfafd5fa4fb0a86ac2af17acedf06d63aa2fdb9601adfdb374d48556a46b95
Tx public key: 820e57185b83bf1572de7f857161ffcc3dda84043ebed823f1763b68d199ff01
Timestamp: 1744739888 Timestamp [UTC]: 2025-04-15 17:58:08 Age [y:d:h:m:s]: 01:217:19:31:14
Block: 1262155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419765 RingCT/type: yes/0
Extra: 01820e57185b83bf1572de7f857161ffcc3dda84043ebed823f1763b68d199ff010211000000056c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6866390fd5b5852a7a3d7d1ccbf829ae5d4bada4badc2b62d1465bcc693a7b6d 0.000600000000 1749332 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": 1262165, "vin": [ { "gen": { "height": 1262155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6866390fd5b5852a7a3d7d1ccbf829ae5d4bada4badc2b62d1465bcc693a7b6d" } } ], "extra": [ 1, 130, 14, 87, 24, 91, 131, 191, 21, 114, 222, 127, 133, 113, 97, 255, 204, 61, 218, 132, 4, 62, 190, 216, 35, 241, 118, 59, 104, 209, 153, 255, 1, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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: