Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc0fa255003ef360cb43a9f37e558e9f5a87fdd694a421d5688be7835a3af02e

Tx prefix hash: 1d1ab883bb31a974e3e86f5f682992a9b2a19176e3a99be79e443d60225597c4
Tx public key: ddccb35be68723083c775ea790f004f440a4cd10244dec04edc644221ba31205
Timestamp: 1576867305 Timestamp [UTC]: 2019-12-20 18:41:45 Age [y:d:h:m:s]: 06:073:07:58:43
Block: 28710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1460062 RingCT/type: yes/0
Extra: 01ddccb35be68723083c775ea790f004f440a4cd10244dec04edc644221ba3120502110000002fd81c26c0000000000000000000

1 output(s) for total of 0.493035084749 xmr

stealth address amount amount idx tag
00: daa00b0d44990fb9987bb45e13715df552c5a36d2e3dc7b314034f08377f2e04 0.493035084749 47420 of 0 -

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": 28720, "vin": [ { "gen": { "height": 28710 } } ], "vout": [ { "amount": 493035084749, "target": { "key": "daa00b0d44990fb9987bb45e13715df552c5a36d2e3dc7b314034f08377f2e04" } } ], "extra": [ 1, 221, 204, 179, 91, 230, 135, 35, 8, 60, 119, 94, 167, 144, 240, 4, 244, 64, 164, 205, 16, 36, 77, 236, 4, 237, 198, 68, 34, 27, 163, 18, 5, 2, 17, 0, 0, 0, 47, 216, 28, 38, 192, 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