Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 967b16224418d44ff42712fbb4d1604cdf01d52074977e6e2dc3333660bcf5d0

Tx prefix hash: 5b03f53697764f7cf6e3acbec7e0c7ed090435cb3cf1c4499e75a911286760ab
Tx public key: 1582c6614f8095588d4b285ae54cb7ad9f2ec21906066c395c5968f87cadb747
Timestamp: 1588737197 Timestamp [UCT]: 2020-05-06 03:53:17 Age [y:d:h:m:s]: 05:024:11:45:59
Block: 99106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1194467 RingCT/type: yes/0
Extra: 011582c6614f8095588d4b285ae54cb7ad9f2ec21906066c395c5968f87cadb7470211000000eb37fb5df4000000000000000000

1 output(s) for total of 288.151871340000 dcy

stealth address amount amount idx
00: b8524e39c06875f6f65a8f42793313eebe6d529157b6a3e1500e072d81c9a206 288.151871340000 174952 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": 99116, "vin": [ { "gen": { "height": 99106 } } ], "vout": [ { "amount": 288151871340, "target": { "key": "b8524e39c06875f6f65a8f42793313eebe6d529157b6a3e1500e072d81c9a206" } } ], "extra": [ 1, 21, 130, 198, 97, 79, 128, 149, 88, 141, 75, 40, 90, 229, 76, 183, 173, 159, 46, 194, 25, 6, 6, 108, 57, 92, 89, 104, 248, 124, 173, 183, 71, 2, 17, 0, 0, 0, 235, 55, 251, 93, 244, 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