← previous blocknext block →recent activity
Analyzing
Block #88,075,926
18 transactions · 15 stateful · 2026-07-16 06:23:45 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,075,926 · 18 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
2w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d2f2e75…e6b6
0x34b655…2a6f
4 touches
1 conflict
0xb6aedce9…a483
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x59dccbd8…2bf6
0x34b655…2a6f
4 touches
1 conflict
0x21d22421…0b7a
0x34b655…2a6f
2 touches
0 conflicts
0x32e4c206…a476
0x34b655…2a6f
2 touches
0 conflicts
0x48719cbe…5484
0x34b655…2a6f
2 touches
0 conflicts
0x6c88e1f7…d3d4
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 0x5d2f2e7584…f1e6b6
Audit this contract →
← previous block·next block →recent activity