← previous blocknext block →recent activity
Analyzing
Block #86,491,187
17 transactions · 16 stateful · 2026-07-08 21:44:59 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,491,187 · 17 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
5w06w17w012w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0xfed6d807…efff
0x34b655…2a6f
4 touches
1 conflict
0x080ec687…da80
0x34b655…2a6f
4 touches
1 conflict
0x469dac8d…3411
0x34b655…2a6f
2 touches
0 conflicts
0x58de7cc7…631c
0x34b655…2a6f
2 touches
0 conflicts
0x65b4fa5f…c1c9
0x34b655…2a6f
2 touches
0 conflicts
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity