Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 950f99af4a7501345c54eaab751237da6458b29223f79805389d482f7f0b589a

Tx prefix hash: 2e700847d0b99a094cac35abfa14775fc01742a658d7c9d11c49ba8554c20042
Tx public key: e5ef396ad7d8e46687c4475af6f05659d41dd875e691a3f10f243d2053f7c63b
Timestamp: 1584759837 Timestamp [UCT]: 2020-03-21 03:03:57 Age [y:d:h:m:s]: 05:070:06:23:23
Block: 85917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1207481 RingCT/type: yes/0
Extra: 01e5ef396ad7d8e46687c4475af6f05659d41dd875e691a3f10f243d2053f7c63b021100000007e1f32f7d000000000000000000

1 output(s) for total of 318.655995726000 dcy

stealth address amount amount idx
00: 40b22eaf44fec8cec1077b59f97e12927dabdd16355af0d92455fa372c8c7876 318.655995726000 155159 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": 85927, "vin": [ { "gen": { "height": 85917 } } ], "vout": [ { "amount": 318655995726, "target": { "key": "40b22eaf44fec8cec1077b59f97e12927dabdd16355af0d92455fa372c8c7876" } } ], "extra": [ 1, 229, 239, 57, 106, 215, 216, 228, 102, 135, 196, 71, 90, 246, 240, 86, 89, 212, 29, 216, 117, 230, 145, 163, 241, 15, 36, 61, 32, 83, 247, 198, 59, 2, 17, 0, 0, 0, 7, 225, 243, 47, 125, 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