Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9cc96e56eb96d0c56ee054e9b6d204cb1d0c7a355c32f24bd4241942b86d007

Tx prefix hash: 50eececbf3f19676ce5d078d85e32729930489d648cd0bbf833888ffe52f5ae5
Tx public key: 61cc2aceeecfabfb93217d3290f0d86dfed0045cc4d11c70795e25e73f32fd04
Timestamp: 1582514411 Timestamp [UCT]: 2020-02-24 03:20:11 Age [y:d:h:m:s]: 04:256:06:07:43
Block: 71325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1075671 RingCT/type: yes/0
Extra: 0161cc2aceeecfabfb93217d3290f0d86dfed0045cc4d11c70795e25e73f32fd040211000000017adf42d3000000000000000000

1 output(s) for total of 356.199490037000 dcy

stealth address amount amount idx
00: 8a962d7ee5ee02cffd4a2188ca285d793ba4412cec2eadd9247e27628bf154fb 356.199490037000 131760 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": 71335, "vin": [ { "gen": { "height": 71325 } } ], "vout": [ { "amount": 356199490037, "target": { "key": "8a962d7ee5ee02cffd4a2188ca285d793ba4412cec2eadd9247e27628bf154fb" } } ], "extra": [ 1, 97, 204, 42, 206, 238, 207, 171, 251, 147, 33, 125, 50, 144, 240, 216, 109, 254, 208, 4, 92, 196, 209, 28, 112, 121, 94, 37, 231, 63, 50, 253, 4, 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