Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 737872f3f9d96d9e794837a4ad9d89bf6177a4133e851805c0cb8edbb731bb75

Tx prefix hash: a7e0943074ecf2caaf665d7af430008272e21f0459a1449fcfffa9e9390b1aa6
Tx public key: a17da3d19fb57a3df3e831fd8f80cdccceca88d677b19df8ad117c11566e90ac
Timestamp: 1581819561 Timestamp [UCT]: 2020-02-16 02:19:21 Age [y:d:h:m:s]: 04:322:15:29:08
Block: 65678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123070 RingCT/type: yes/0
Extra: 01a17da3d19fb57a3df3e831fd8f80cdccceca88d677b19df8ad117c11566e90ac0211000000017adf42d3000000000000000000

1 output(s) for total of 371.862454691000 dcy

stealth address amount amount idx
00: fba712d4e6e281707c27f803a6e2bf423f3a0de0aaf2ead4814bd04aacf1f2a0 371.862454691000 121221 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": 65688, "vin": [ { "gen": { "height": 65678 } } ], "vout": [ { "amount": 371862454691, "target": { "key": "fba712d4e6e281707c27f803a6e2bf423f3a0de0aaf2ead4814bd04aacf1f2a0" } } ], "extra": [ 1, 161, 125, 163, 209, 159, 181, 122, 61, 243, 232, 49, 253, 143, 128, 205, 204, 206, 202, 136, 214, 119, 177, 157, 248, 173, 17, 124, 17, 86, 110, 144, 172, 2, 17, 0, 0, 0, 1, 122, 223, 66, 211, 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