Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 613cd21f79a47b10f5da4cab0d2e5affc6a69ed60a16c6d5da5f7cde585ec172

Tx prefix hash: 576df0effd0b16f11183021ebc082f836e34fb66ec4eb3a6b98df0d0a37bb9b0
Tx public key: bc7a594454a3e287e8f668d0de3e7501fc5bd6665c0097c85b8bf2891d32b383
Timestamp: 1770882919 Timestamp [UTC]: 2026-02-12 07:55:19 Age [y:d:h:m:s]: 00:276:07:06:00
Block: 1476082 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202886 RingCT/type: yes/0
Extra: 01bc7a594454a3e287e8f668d0de3e7501fc5bd6665c0097c85b8bf2891d32b383021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9fae3dcec000445df8f4ea7ee7fd974c3571a556da59ecd3eb849f610425f751 0.000600000000 1965386 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": 1476092, "vin": [ { "gen": { "height": 1476082 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fae3dcec000445df8f4ea7ee7fd974c3571a556da59ecd3eb849f610425f751" } } ], "extra": [ 1, 188, 122, 89, 68, 84, 163, 226, 135, 232, 246, 104, 208, 222, 62, 117, 1, 252, 91, 214, 102, 92, 0, 151, 200, 91, 139, 242, 137, 29, 50, 179, 131, 2, 17, 0, 0, 0, 6, 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: