Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec966c1221a8066afb080bfd4afbed8b00ae689dc37bccde05359da883efc798

Tx prefix hash: a02440201698e0d91b5db9065142a05aaf9f6b0a15ce4d06c1cf70889d9bbef5
Tx public key: a3c1a873dce69c1ef146b857173aa2272db7bf971d327f36853bdfff5c25fe43
Timestamp: 1754927780 Timestamp [UTC]: 2025-08-11 15:56:20 Age [y:d:h:m:s]: 00:274:04:21:57
Block: 1344903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187443 RingCT/type: yes/0
Extra: 01a3c1a873dce69c1ef146b857173aa2272db7bf971d327f36853bdfff5c25fe4302110000000db2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9935a2a82c611848885b455e1aa15df2681d8d3196656df45bfebb33ed57c283 0.000600000000 1832790 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": 1344913, "vin": [ { "gen": { "height": 1344903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9935a2a82c611848885b455e1aa15df2681d8d3196656df45bfebb33ed57c283" } } ], "extra": [ 1, 163, 193, 168, 115, 220, 230, 156, 30, 241, 70, 184, 87, 23, 58, 162, 39, 45, 183, 191, 151, 29, 50, 127, 54, 133, 59, 223, 255, 92, 37, 254, 67, 2, 17, 0, 0, 0, 13, 178, 247, 132, 196, 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: