Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f46a8914d0d3099741d2aed0a2fe0cd4b0b7e64ff252ec6656f265a579a2103c

Tx prefix hash: 1e717dbb6fc13d9b3dc294fcb31b0c72e419d373cf3357ebcc881612803cbcc5
Tx public key: 6127016b37fe18da36e98d32171b5981fc8bfc54106bfcd39c2bf7ba250c4bb3
Timestamp: 1744631835 Timestamp [UTC]: 2025-04-14 11:57:15 Age [y:d:h:m:s]: 01:213:21:02:33
Block: 1261262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416768 RingCT/type: yes/0
Extra: 016127016b37fe18da36e98d32171b5981fc8bfc54106bfcd39c2bf7ba250c4bb30211000000036c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 558ef097ac6484c0606b32f88df67933d1a79962660b56f26d63da1217fe52fd 0.000600000000 1748431 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": 1261272, "vin": [ { "gen": { "height": 1261262 } } ], "vout": [ { "amount": 600000000, "target": { "key": "558ef097ac6484c0606b32f88df67933d1a79962660b56f26d63da1217fe52fd" } } ], "extra": [ 1, 97, 39, 1, 107, 55, 254, 24, 218, 54, 233, 141, 50, 23, 27, 89, 129, 252, 139, 252, 84, 16, 107, 252, 211, 156, 43, 247, 186, 37, 12, 75, 179, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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: