Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e6f1405733a7916ec3531e749fd1f3673e4328a6bf48872ac01a6a737f05151

Tx prefix hash: 28e201778a929289f2edc173ceb1630a947d08fb4ef4664cf9e5102c732e698f
Tx public key: 64987bc11a5468df464e24522989d1ea88440ca5ffb1149e54c1a4e1d6bc4647
Timestamp: 1705159607 Timestamp [UTC]: 2024-01-13 15:26:47 Age [y:d:h:m:s]: 02:124:13:18:59
Block: 934504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 601117 RingCT/type: yes/0
Extra: 0164987bc11a5468df464e24522989d1ea88440ca5ffb1149e54c1a4e1d6bc464702110000000752d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8f3358fe0c769f39d2299a679a96e7a1df3f2b7ca0ee3bf495ca2d89fcd02168 0.000600000000 1392518 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": 934514, "vin": [ { "gen": { "height": 934504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f3358fe0c769f39d2299a679a96e7a1df3f2b7ca0ee3bf495ca2d89fcd02168" } } ], "extra": [ 1, 100, 152, 123, 193, 26, 84, 104, 223, 70, 78, 36, 82, 41, 137, 209, 234, 136, 68, 12, 165, 255, 177, 20, 158, 84, 193, 164, 225, 214, 188, 70, 71, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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: