← previous blocknext block →recent activity
Analyzing
Block #88,350,908
20 transactions · 16 stateful · 2026-07-17 13:03:35 UTC
Parallelism
85/100
Blocked
19%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,350,908 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w18w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf75e37ca…197b
0x34b655…2a6f
4 touches
1 conflict
0x8b818135…eff8
0x34b655…2a6f
4 touches
1 conflict
0xc68a85d2…f045
0x34b655…2a6f
4 touches
1 conflict
0xc68a85d2…f046
0x34b655…2a6f
4 touches
1 conflict
0xd8675136…9a01
0x34b655…2a6f
4 touches
1 conflict
0xd9512d97…be3d
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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
1 conflict on slot 0xf75e37ca3e…36197b
Audit this contract →
← previous block·next block →recent activity