← previous blocknext block →recent activity
Analyzing
Block #88,350,417
15 transactions · 13 stateful · 2026-07-17 13:00:18 UTC
Parallelism
87/100
Blocked
8%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #88,350,417 · 15 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
4w06w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e70dadd…810d
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810e
0x34b655…2a6f
4 touches
1 conflict
0x2b856d86…7988
0x34b655…2a6f
4 touches
1 conflict
0xcc282b3d…e139
0x34b655…2a6f
4 touches
1 conflict
0xcf1181d6…e83f
0x34b655…2a6f
4 touches
1 conflict
0xd5ab2f5b…092b
0x34b655…2a6f
4 touches
1 conflict
0x072f36ce…7ecf
0x34b655…2a6f
4 touches
1 conflict
0xa70f4869…febb
0x34b655…2a6f
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 0x9e70dadd35…1b810d
Audit this contract →
← previous block·next block →recent activity