← previous blocknext block →recent activity
Analyzing
Block #88,093,072
24 transactions · 18 stateful · 2026-07-16 08:18:27 UTC
Parallelism
71/100
Blocked
39%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #88,093,072 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
10w012w114w219w220w321w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d989c17…e984
0x34b655…2a6f
12 touches
15 conflicts
0x40a81b78…095d
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x6fc24f20…f3c7
0x34b655…2a6f
6 touches
3 conflicts
0x04a566e1…26f3
0x34b655…2a6f
6 touches
3 conflicts
0x02060180…fe50
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
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
15 conflicts on slot 0x8d989c177f…b7e984
Audit this contract →
← previous block·next block →recent activity