← previous blocknext block →recent activity
Analyzing
Block #88,363,916
18 transactions · 16 stateful · 2026-07-17 14:31:11 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,363,916 · 18 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
1w02w16w07w19w110w213w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ef0952c…762d
0x34b655…2a6f
10 touches
10 conflicts
0x2029b74e…c206
0x34b655…2a6f
4 touches
1 conflict
0x258fcaf5…2084
0x34b655…2a6f
4 touches
1 conflict
0x2d651956…12e8
0x34b655…2a6f
4 touches
1 conflict
0x2f461725…5ab2
0x34b655…2a6f
4 touches
1 conflict
0x436d1382…f410
0x34b655…2a6f
4 touches
1 conflict
0x57acd0c7…48bc
0x34b655…2a6f
4 touches
1 conflict
0x59e84008…7fac
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 0x3ef0952c66…03762d
Audit this contract →
← previous block·next block →recent activity