Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dac21bac463a0a49145e867a8db35ac1087a5c01061a1afa1cb420fee502474

Tx prefix hash: d8b899595f3430da0fb8b532a8de0c4243118d6c8d3a66e2ac77c0492ea485f6
Tx public key: 7bf0e5d97504fe8cecfddb9cca52990274d68328b6bd82abbe426524319b4d66
Timestamp: 1577524666 Timestamp [UCT]: 2019-12-28 09:17:46 Age [y:d:h:m:s]: 05:038:02:44:09
Block: 33324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1177156 RingCT/type: yes/0
Extra: 017bf0e5d97504fe8cecfddb9cca52990274d68328b6bd82abbe426524319b4d66021100000012ad433a0b000000000000000000

1 output(s) for total of 475.975514480000 dcy

stealth address amount amount idx
00: 63b5161eba1e0dcde050c0094b0f8b3b91bce7649f08ea22448c6564f1bf12d7 475.975514480000 55776 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": 33334, "vin": [ { "gen": { "height": 33324 } } ], "vout": [ { "amount": 475975514480, "target": { "key": "63b5161eba1e0dcde050c0094b0f8b3b91bce7649f08ea22448c6564f1bf12d7" } } ], "extra": [ 1, 123, 240, 229, 217, 117, 4, 254, 140, 236, 253, 219, 156, 202, 82, 153, 2, 116, 214, 131, 40, 182, 189, 130, 171, 190, 66, 101, 36, 49, 155, 77, 102, 2, 17, 0, 0, 0, 18, 173, 67, 58, 11, 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