Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75e08fd8a7e8f803e54cf8c8212d3e5120f5d3b957b471c3095b20e286f2f4a1

Tx prefix hash: cf75efc6000d8dee8d5924fb4335d76edb677fc5ed089cf7fb6f6ec996a9a703
Tx public key: 06a25b22cba8b47cb4e4dbd908ccab38b6efdc70a352271af7dfc9141a159d9e
Timestamp: 1746106454 Timestamp [UTC]: 2025-05-01 13:34:14 Age [y:d:h:m:s]: 01:013:01:38:50
Block: 1273462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260223 RingCT/type: yes/0
Extra: 0106a25b22cba8b47cb4e4dbd908ccab38b6efdc70a352271af7dfc9141a159d9e021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7545303269b053237803ad9bc20e5a28e2093c30f122b8b0216cfeda9c5650a8 0.000600000000 1760745 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": 1273472, "vin": [ { "gen": { "height": 1273462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7545303269b053237803ad9bc20e5a28e2093c30f122b8b0216cfeda9c5650a8" } } ], "extra": [ 1, 6, 162, 91, 34, 203, 168, 180, 124, 180, 228, 219, 217, 8, 204, 171, 56, 182, 239, 220, 112, 163, 82, 39, 26, 247, 223, 201, 20, 26, 21, 157, 158, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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: