← previous blocknext block →recent activity
Analyzing
Block #87,409,452
19 transactions · 18 stateful · 2026-07-13 04:05:23 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
0.89
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,409,452 · 19 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
1w02w03w05w07w08w110w111w212w113w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
6 touches
3 conflicts
0x05ef50ec…7052
0x34b655…2a6f
4 touches
1 conflict
0x086db8fc…0024
0x34b655…2a6f
4 touches
1 conflict
0x0aa5b76b…60db
0x34b655…2a6f
4 touches
1 conflict
0x2b5101ac…090b
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity