Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a25f4baf43f2d4661c02df61040ca11e5c695644d9f8acacd4ffc761dd59cae

Tx prefix hash: 4377ae8dcc902b2a54b1c9c6c183f93c299ed802eae2601f202d9b35b421ee4a
Tx public key: 8899467220cf18df708eb4690adc05ecaf698b0bb6d8f8829fc82b0e64ce0c70
Timestamp: 1774409483 Timestamp [UTC]: 2026-03-25 03:31:23 Age [y:d:h:m:s]: 00:047:18:38:44
Block: 1505230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26410 RingCT/type: yes/0
Extra: 018899467220cf18df708eb4690adc05ecaf698b0bb6d8f8829fc82b0e64ce0c70021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6ba0c2dace9c518287a3c7de9ad039ddd0948fe5c1d69b046b262d284406c117 0.000600000000 1994962 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": 1505240, "vin": [ { "gen": { "height": 1505230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ba0c2dace9c518287a3c7de9ad039ddd0948fe5c1d69b046b262d284406c117" } } ], "extra": [ 1, 136, 153, 70, 114, 32, 207, 24, 223, 112, 142, 180, 105, 10, 220, 5, 236, 175, 105, 139, 11, 182, 216, 248, 130, 159, 200, 43, 14, 100, 206, 12, 112, 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: