← previous blocknext block →recent activity
Analyzing
Block #83,640,712
19 transactions · 15 stateful · 2026-06-25 16:57:54 UTC
Parallelism
68/100
Blocked
33%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,640,712 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w29w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda5e0705…ecb9
0x34b655…2a6f
10 touches
10 conflicts
0xffb1ee54…7c2c
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xc5766a3b…989c
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x93641233…06f5
0x34b655…2a6f
5 touches
3 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
4 touches
1 conflict
0x7fe97198…79ab
0x34b655…2a6f
4 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
10 conflicts on slot 0xda5e0705c4…a5ecb9
Audit this contract →
← previous block·next block →recent activity