Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee9f2ee6bf5dd95a944b91552d5a0fed080b133dcb0bb9ef7189adf37ffe745c

Tx prefix hash: 7a7d3d07878015033e0662dadcd1b799842433a879b9e757db5c5f9c91fa3e33
Tx public key: 7d2f92640b5e7f63e78b91058ded1ab52a0f05031a4c4df8b1f43363f259b64f
Timestamp: 1708971863 Timestamp [UTC]: 2024-02-26 18:24:23 Age [y:d:h:m:s]: 02:015:18:23:42
Block: 966132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 530801 RingCT/type: yes/0
Extra: 017d2f92640b5e7f63e78b91058ded1ab52a0f05031a4c4df8b1f43363f259b64f02110000000652d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bd205845de4b551e8f9453febbdafcd4db20a242fe975d1376412117f63b813a 0.000600000000 1425889 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": 966142, "vin": [ { "gen": { "height": 966132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd205845de4b551e8f9453febbdafcd4db20a242fe975d1376412117f63b813a" } } ], "extra": [ 1, 125, 47, 146, 100, 11, 94, 127, 99, 231, 139, 145, 5, 141, 237, 26, 181, 42, 15, 5, 3, 26, 76, 77, 248, 177, 244, 51, 99, 242, 89, 182, 79, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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) | dinastycoin version: tesla-369