Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 201a3f4b1bd73a39950cb272b1d5b21e082f38fd17fda2de64113bd219027862

Tx prefix hash: 09ce1b0af3a17c899bb04a2f6245f6dc2a8190e6de280f61091900a7c7af84d9
Tx public key: 5fe9f39d208dc483c2d4e7a2ceaaeb75c0ccccd7e72baac1e505e4163b000a80
Timestamp: 1729938908 Timestamp [UTC]: 2024-10-26 10:35:08 Age [y:d:h:m:s]: 02:024:01:36:16
Block: 1139928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541951 RingCT/type: yes/0
Extra: 015fe9f39d208dc483c2d4e7a2ceaaeb75c0ccccd7e72baac1e505e4163b000a800211000000101f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 662add0536644a5d726b3655a63d2237a69e9ff59c91b1ae633dfcaa38e9506b 0.000600000000 1623715 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": 1139938, "vin": [ { "gen": { "height": 1139928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "662add0536644a5d726b3655a63d2237a69e9ff59c91b1ae633dfcaa38e9506b" } } ], "extra": [ 1, 95, 233, 243, 157, 32, 141, 196, 131, 194, 212, 231, 162, 206, 170, 235, 117, 192, 204, 204, 215, 231, 43, 170, 193, 229, 5, 228, 22, 59, 0, 10, 128, 2, 17, 0, 0, 0, 16, 31, 10, 83, 235, 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: