Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a60fdb734f9711f9297478e445fbd4c3f799f07f07b2ef644df4f688ef6ef35d

Tx prefix hash: 819c41cd240645db4d5acb257fb04f41a8cb1612ad5e5876080ea59b30d3fb93
Tx public key: 20540375ec9ae6589e6a8033cef0c2de9bbacdaf1d6ec696170edef7698355ef
Timestamp: 1747762890 Timestamp [UTC]: 2025-05-20 17:41:30 Age [y:d:h:m:s]: 01:182:16:54:32
Block: 1287188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394635 RingCT/type: yes/0
Extra: 0120540375ec9ae6589e6a8033cef0c2de9bbacdaf1d6ec696170edef7698355ef0211000000039f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 519dbe78d15b992d643c0dc0a82b1571733f19a8956918d8fa9c13a915164eed 0.000600000000 1774655 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": 1287198, "vin": [ { "gen": { "height": 1287188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "519dbe78d15b992d643c0dc0a82b1571733f19a8956918d8fa9c13a915164eed" } } ], "extra": [ 1, 32, 84, 3, 117, 236, 154, 230, 88, 158, 106, 128, 51, 206, 240, 194, 222, 155, 186, 205, 175, 29, 110, 198, 150, 23, 14, 222, 247, 105, 131, 85, 239, 2, 17, 0, 0, 0, 3, 159, 159, 230, 140, 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: