Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1be0b6e208540aea5731b692056d10b03bad1c003f2d21973ac64a31d4772c4

Tx prefix hash: f9a30ff78d628b4a20a72dc9e1325d900bf772b5cd9350c3dd5d62b24938807c
Tx public key: fd64453d5f36ce2391ec4e5ee9db817617627ca15b02e240d7294667eae70c81
Timestamp: 1635076654 Timestamp [UCT]: 2021-10-24 11:57:34 Age [y:d:h:m:s]: 03:064:16:06:11
Block: 359483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 824560 RingCT/type: yes/0
Extra: 01fd64453d5f36ce2391ec4e5ee9db817617627ca15b02e240d7294667eae70c810211000000014a0f5013000000000000000000

1 output(s) for total of 39.527483380000 dcy

stealth address amount amount idx
00: 35eab1c23089631cd3ebae993c179f0a3edbc1b7e11356dcba2db65bf55f3b68 39.527483380000 732022 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": 359493, "vin": [ { "gen": { "height": 359483 } } ], "vout": [ { "amount": 39527483380, "target": { "key": "35eab1c23089631cd3ebae993c179f0a3edbc1b7e11356dcba2db65bf55f3b68" } } ], "extra": [ 1, 253, 100, 69, 61, 95, 54, 206, 35, 145, 236, 78, 94, 233, 219, 129, 118, 23, 98, 124, 161, 91, 2, 226, 64, 215, 41, 70, 103, 234, 231, 12, 129, 2, 17, 0, 0, 0, 1, 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