Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00a8606fb32a2db48b65e22a858479aa1a78979009fc66fccf91eeee91a431ac

Tx prefix hash: bcab43a764a5a8a2034984b7f7839ec332af7aa9e6c18d0b76cc201ba6938941
Tx public key: 929ff0752d19847eed2451b7c0aa52b0e1f3fab6e157492100b2d18f97303657
Timestamp: 1770236749 Timestamp [UTC]: 2026-02-04 20:25:49 Age [y:d:h:m:s]: 00:285:04:17:18
Block: 1470735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209294 RingCT/type: yes/0
Extra: 01929ff0752d19847eed2451b7c0aa52b0e1f3fab6e157492100b2d18f97303657021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e16aaf94063295df1e0f6e1656eeb2f85b32312dbf313e41671acb183b8fc374 0.000600000000 1960003 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": 1470745, "vin": [ { "gen": { "height": 1470735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e16aaf94063295df1e0f6e1656eeb2f85b32312dbf313e41671acb183b8fc374" } } ], "extra": [ 1, 146, 159, 240, 117, 45, 25, 132, 126, 237, 36, 81, 183, 192, 170, 82, 176, 225, 243, 250, 182, 225, 87, 73, 33, 0, 178, 209, 143, 151, 48, 54, 87, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 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: