← previous blocknext block →recent activity
Analyzing
Block #87,671,417
15 transactions · 14 stateful · 2026-07-14 09:17:50 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,671,417 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w17w210w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xd8eb2d31…2ac0
0xea1b8e…c5ec
4 touches
1 conflict
0xeef70cb9…5de7
0xea1b8e…c5ec
4 touches
1 conflict
0xfecd05e7…296f
0xea1b8e…c5ec
4 touches
1 conflict
0xfecd05e7…2970
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x9560013d…8caf
0xfd44b3…00d1
4 touches
1 conflict
0xd732a18c…9ffa
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity