Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 369b3a3746c77fd345626a73e9407eb16ddc657e1fc88fa273269a7e0bc12314

Tx prefix hash: ea2b389ec017a73e2fcf9c2b340580b25ae665db4011946dee621831600b91fb
Tx public key: 6e6ab8f30c8def8a100871fbca2dd1c07d8293db8fd3cf6e01bab43fac2489bd
Timestamp: 1745691191 Timestamp [UTC]: 2025-04-26 18:13:11 Age [y:d:h:m:s]: 01:205:23:28:54
Block: 1270043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411241 RingCT/type: yes/0
Extra: 016e6ab8f30c8def8a100871fbca2dd1c07d8293db8fd3cf6e01bab43fac2489bd021100000008f7011ad5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 31b81a1c7194162fc74c4ad10ab9e1e9bf8278f1340d93bbace6f47cc6238330 0.000600000000 1757284 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": 1270053, "vin": [ { "gen": { "height": 1270043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31b81a1c7194162fc74c4ad10ab9e1e9bf8278f1340d93bbace6f47cc6238330" } } ], "extra": [ 1, 110, 106, 184, 243, 12, 141, 239, 138, 16, 8, 113, 251, 202, 45, 209, 192, 125, 130, 147, 219, 143, 211, 207, 110, 1, 186, 180, 63, 172, 36, 137, 189, 2, 17, 0, 0, 0, 8, 247, 1, 26, 213, 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: