Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6642438674a202d75c9b8b30724820ca122568f1345f2256c0ff91763d19c24b

Tx prefix hash: e89754f89375d71f8210ce8f6d61e592bebfd0d7f593093394f879a143f3e8f9
Tx public key: 1bf617ac5b9e5de2e6aac2c42e11e0d611794ccf7a192587e927f436164f9efc
Timestamp: 1580018531 Timestamp [UCT]: 2020-01-26 06:02:11 Age [y:d:h:m:s]: 04:311:16:45:44
Block: 53308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1112700 RingCT/type: yes/0
Extra: 011bf617ac5b9e5de2e6aac2c42e11e0d611794ccf7a192587e927f436164f9efc02110000000449b77a3d000000000000000000

1 output(s) for total of 408.666741446000 dcy

stealth address amount amount idx
00: af9d5a0980712fce5c02f4d0e796f1d7c5f7d6e22b6dcae9f60b2ed6d083077d 408.666741446000 98762 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": 53318, "vin": [ { "gen": { "height": 53308 } } ], "vout": [ { "amount": 408666741446, "target": { "key": "af9d5a0980712fce5c02f4d0e796f1d7c5f7d6e22b6dcae9f60b2ed6d083077d" } } ], "extra": [ 1, 27, 246, 23, 172, 91, 158, 93, 226, 230, 170, 194, 196, 46, 17, 224, 214, 17, 121, 76, 207, 122, 25, 37, 135, 233, 39, 244, 54, 22, 79, 158, 252, 2, 17, 0, 0, 0, 4, 73, 183, 122, 61, 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