Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dddb724e0c7fa7306e4ee70574c711b2657104c3db649cb3e0acdfc94232e329

Tx prefix hash: 6fafef6928f2613b9294880180fe892cfbd33d685cf8c19246f8f191613bcc1e
Tx public key: 7df6ce9432b3c22eb964a10ac509f4d7395cb6c163b96a985e94be74714029f5
Timestamp: 1583851894 Timestamp [UCT]: 2020-03-10 14:51:34 Age [y:d:h:m:s]: 04:311:17:16:52
Block: 79814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117937 RingCT/type: yes/0
Extra: 017df6ce9432b3c22eb964a10ac509f4d7395cb6c163b96a985e94be74714029f5021100000002640ff48f000000000000000000

1 output(s) for total of 333.844231038000 dcy

stealth address amount amount idx
00: af96ad28565bc607ffd8b5ff858fab60c7c58df26a464c986e0ccf4af54af9b4 333.844231038000 146038 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 dinasty-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": 79824, "vin": [ { "gen": { "height": 79814 } } ], "vout": [ { "amount": 333844231038, "target": { "key": "af96ad28565bc607ffd8b5ff858fab60c7c58df26a464c986e0ccf4af54af9b4" } } ], "extra": [ 1, 125, 246, 206, 148, 50, 179, 194, 46, 185, 100, 161, 10, 197, 9, 244, 215, 57, 92, 182, 193, 99, 185, 106, 152, 94, 148, 190, 116, 113, 64, 41, 245, 2, 17, 0, 0, 0, 2, 100, 15, 244, 143, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8