← previous blocknext block →recent activity
Analyzing
Block #83,762,565
18 transactions · 16 stateful · 2026-06-26 06:30:49 UTC
Parallelism
89/100
Blocked
19%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,762,565 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w011w012w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4994f59…060c
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xa9db7b4d…2957
0x40c49f…2af0
4 touches
1 conflict
0xdfc5f346…7b42
0x40c49f…2af0
4 touches
1 conflict
0x99220815…6ba7
0x40c49f…2af0
3 touches
1 conflict
0x12414d98…166a
0x40c49f…2af0
3 touches
1 conflict
0x7a28ef8a…593f
0x40c49f…2af0
3 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0xa4994f5988…0f060c
Audit this contract →
← previous block·next block →recent activity