Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd6d600a96e2cb8ed5c4ab0414a8522db67d43398005f8ba319045ad0c98b731

Tx prefix hash: 4dcd285e8aaf961537f9f5792f0f6e734f7118f51761b320558a6a677e27ed96
Tx public key: 28ef67ca6916ee4a89044396db5c2808a276e3bee929edec2bb3b8081344fc61
Timestamp: 1588737024 Timestamp [UCT]: 2020-05-06 03:50:24 Age [y:d:h:m:s]: 05:179:16:54:06
Block: 99035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1303138 RingCT/type: yes/0
Extra: 0128ef67ca6916ee4a89044396db5c2808a276e3bee929edec2bb3b8081344fc6102110000015aa86a1a65000000000000000000

1 output(s) for total of 288.308002345000 dcy

stealth address amount amount idx
00: 84fa7ffbf449d72b319f01284cf6d9924f432402d1d21c125e79c01fd5865aa5 288.308002345000 174869 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": 99045, "vin": [ { "gen": { "height": 99035 } } ], "vout": [ { "amount": 288308002345, "target": { "key": "84fa7ffbf449d72b319f01284cf6d9924f432402d1d21c125e79c01fd5865aa5" } } ], "extra": [ 1, 40, 239, 103, 202, 105, 22, 238, 74, 137, 4, 67, 150, 219, 92, 40, 8, 162, 118, 227, 190, 233, 41, 237, 236, 43, 179, 184, 8, 19, 68, 252, 97, 2, 17, 0, 0, 1, 90, 168, 106, 26, 101, 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