Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd36320266f80a7e34a8f76987814840ef98bb15daf23f3b279d252009ea443c

Tx prefix hash: 52789ea3baceeb4bf983c4fb0dc205df55006ccfdd050a9930de5b0740fae45f
Tx public key: e5b6451fdf6e934873dc3355db4ac8751fd16979a067f0671fcdec3a1f8bb57c
Timestamp: 1743836562 Timestamp [UTC]: 2025-04-05 07:02:42 Age [y:d:h:m:s]: 01:230:03:09:46
Block: 1254678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428666 RingCT/type: yes/0
Extra: 01e5b6451fdf6e934873dc3355db4ac8751fd16979a067f0671fcdec3a1f8bb57c0211000000044060f6d2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3837d51dbf8a17d891147e170c6141b80f4d1a2b4bf7dc551db5f4acaec2e436 0.000600000000 1741759 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": 1254688, "vin": [ { "gen": { "height": 1254678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3837d51dbf8a17d891147e170c6141b80f4d1a2b4bf7dc551db5f4acaec2e436" } } ], "extra": [ 1, 229, 182, 69, 31, 223, 110, 147, 72, 115, 220, 51, 85, 219, 74, 200, 117, 31, 209, 105, 121, 160, 103, 240, 103, 31, 205, 236, 58, 31, 139, 181, 124, 2, 17, 0, 0, 0, 4, 64, 96, 246, 210, 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: