Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1dd2c3f6f46619a6de83875d21b0b9eb23776f8e5c2deb84d341de5374946dc

Tx prefix hash: f3687d90467dc3d57eb6bb9a6b0e4a0fac208fbc0228d0bd897b64b0b533037c
Tx public key: 26ad28e75ea0732fdb5db4d032bfdf792ec7e9464b1b7097d6440890b34bae05
Timestamp: 1645585223 Timestamp [UCT]: 2022-02-23 03:00:23 Age [y:d:h:m:s]: 03:251:08:18:38
Block: 444480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 957414 RingCT/type: yes/0
Extra: 0126ad28e75ea0732fdb5db4d032bfdf792ec7e9464b1b7097d6440890b34bae050211000000074a0f5013000000000000000000

1 output(s) for total of 20.665862450000 dcy

stealth address amount amount idx
00: 51717c0e38378837f199b95ff8900255dd1d250b702f42bc7664fef312ff8c06 20.665862450000 857777 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": 444490, "vin": [ { "gen": { "height": 444480 } } ], "vout": [ { "amount": 20665862450, "target": { "key": "51717c0e38378837f199b95ff8900255dd1d250b702f42bc7664fef312ff8c06" } } ], "extra": [ 1, 38, 173, 40, 231, 94, 160, 115, 47, 219, 93, 180, 208, 50, 191, 223, 121, 46, 199, 233, 70, 75, 27, 112, 151, 214, 68, 8, 144, 179, 75, 174, 5, 2, 17, 0, 0, 0, 7, 74, 15, 80, 19, 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