Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11181ea4de8f6f75cdabd90bc2a625d3894389a01632a7320cca825936a5a586

Tx prefix hash: 4a3046ddb9f72f0a9682f339493b535cb8419d3f139f481229b27f12b91827f9
Tx public key: 198dd8df2474517fe28883b13ac4589b5c61b01fa65546570a763e6f201d6f5c
Timestamp: 1589361040 Timestamp [UCT]: 2020-05-13 09:10:40 Age [y:d:h:m:s]: 04:337:07:15:08
Block: 100190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1161205 RingCT/type: yes/0
Extra: 01198dd8df2474517fe28883b13ac4589b5c61b01fa65546570a763e6f201d6f5c02110000038586362411000000000000000000

1 output(s) for total of 285.778597660000 dcy

stealth address amount amount idx
00: e7424f2d3969b4acc8f3d39cb1d6693e36bc5962f42da3ecbcb90fdf0061657b 285.778597660000 176654 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": 100200, "vin": [ { "gen": { "height": 100190 } } ], "vout": [ { "amount": 285778597660, "target": { "key": "e7424f2d3969b4acc8f3d39cb1d6693e36bc5962f42da3ecbcb90fdf0061657b" } } ], "extra": [ 1, 25, 141, 216, 223, 36, 116, 81, 127, 226, 136, 131, 177, 58, 196, 88, 155, 92, 97, 176, 31, 166, 85, 70, 87, 10, 118, 62, 111, 32, 29, 111, 92, 2, 17, 0, 0, 3, 133, 134, 54, 36, 17, 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