Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fe74313fe27bfee67b6dc1133e1650d9ab26c3f9c6141bfd29a58d19417c904

Tx prefix hash: 27291e5ce9c43e6951ffeebd3d685f21c1247f518ee152d0879cadca5524deac
Tx public key: 218e4bf305ee6dd986d673fd3a28f7ebaf1ff0bb7d8f65f83dd78399cbba236c
Timestamp: 1744319543 Timestamp [UTC]: 2025-04-10 21:12:23 Age [y:d:h:m:s]: 01:164:03:30:06
Block: 1258671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382049 RingCT/type: yes/0
Extra: 01218e4bf305ee6dd986d673fd3a28f7ebaf1ff0bb7d8f65f83dd78399cbba236c021100000002a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d47f46cb3314e0c081750a35df3c034e922b9ace9233287db35283696059a634 0.000600000000 1745808 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": 1258681, "vin": [ { "gen": { "height": 1258671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d47f46cb3314e0c081750a35df3c034e922b9ace9233287db35283696059a634" } } ], "extra": [ 1, 33, 142, 75, 243, 5, 238, 109, 217, 134, 214, 115, 253, 58, 40, 247, 235, 175, 31, 240, 187, 125, 143, 101, 248, 61, 215, 131, 153, 203, 186, 35, 108, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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: