← previous blocknext block →recent activity
Analyzing
Block #87,306,605
13 transactions · 12 stateful · 2026-07-12 16:37:32 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,306,605 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w09w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b39d0fb…013c
0x34b655…2a6f
4 touches
1 conflict
0xa013ecc1…7c8f
0x34b655…2a6f
4 touches
1 conflict
0xa05444cf…cd70
0x34b655…2a6f
4 touches
1 conflict
0xf9e23360…8ef7
0x34b655…2a6f
4 touches
1 conflict
0x2e4e7336…e906
0x34b655…2a6f
4 touches
1 conflict
0x4f858307…7642
0x34b655…2a6f
4 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
2 touches
0 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
2 touches
0 conflicts
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 0x5b39d0fb82…5a013c
Audit this contract →
← previous block·next block →recent activity