Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa5bae9694a4eaaaab91c8deb75ad9bca4c695f6cebc89956c996e9db6442314

Tx prefix hash: ef3d92803a10c49a783a3b3fff88371eb7b12fcc2ef30bbd4add64e5959188f6
Tx public key: 04b01ec6df2d2b2353c7be5b6a9ff7560a4863381116e190b23ddea8fe6f293f
Timestamp: 1580788200 Timestamp [UCT]: 2020-02-04 03:50:00 Age [y:d:h:m:s]: 04:330:08:43:38
Block: 58186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127537 RingCT/type: yes/0
Extra: 0104b01ec6df2d2b2353c7be5b6a9ff7560a4863381116e190b23ddea8fe6f293f021100000002bd0f9f9f000000000000000000

1 output(s) for total of 393.737200254000 dcy

stealth address amount amount idx
00: 56555760916080c1c7446ecf32244ec45d95eb10f490a55b75c152c615a22965 393.737200254000 107558 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": 58196, "vin": [ { "gen": { "height": 58186 } } ], "vout": [ { "amount": 393737200254, "target": { "key": "56555760916080c1c7446ecf32244ec45d95eb10f490a55b75c152c615a22965" } } ], "extra": [ 1, 4, 176, 30, 198, 223, 45, 43, 35, 83, 199, 190, 91, 106, 159, 247, 86, 10, 72, 99, 56, 17, 22, 225, 144, 178, 61, 222, 168, 254, 111, 41, 63, 2, 17, 0, 0, 0, 2, 189, 15, 159, 159, 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