← previous blocknext block →recent activity
Analyzing
Block #87,303,011
13 transactions · 11 stateful · 2026-07-12 16:13:31 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,303,011 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w17w29w110w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ad87bfc…c47a
0x34b655…2a6f
4 touches
1 conflict
0x1e22ba11…b783
0x34b655…2a6f
4 touches
1 conflict
0x280b9708…a763
0x34b655…2a6f
4 touches
1 conflict
0x430b92ea…6f54
0x34b655…2a6f
4 touches
1 conflict
0x430b92ea…6f55
0x34b655…2a6f
4 touches
1 conflict
0x4c8319f0…212b
0x34b655…2a6f
4 touches
1 conflict
0x5f689f7f…d18e
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
1 conflict on slot 0x0ad87bfc34…e9c47a
Audit this contract →
← previous block·next block →recent activity