← previous blocknext block →recent activity
Analyzing
Block #87,911,376
22 transactions · 21 stateful · 2026-07-15 12:03:12 UTC
Parallelism
68/100
Blocked
38%
Avg conflicts / tx
0.91
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,911,376 · 22 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
1w02w18w010w011w112w213w314w116w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xc36fa358…24cb
0x34b655…2a6f
10 touches
10 conflicts
0x72880226…1435
0x34b655…2a6f
10 touches
10 conflicts
0x2029b74e…c206
0x34b655…2a6f
4 touches
1 conflict
0x30bee766…3c99
0x34b655…2a6f
4 touches
1 conflict
0x35cfae1b…c1f8
0x34b655…2a6f
4 touches
1 conflict
0x477df9ac…189c
0x34b655…2a6f
4 touches
1 conflict
0x7c6cfc14…9957
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity