← previous blocknext block →recent activity
Analyzing
Block #87,316,728
12 transactions · 12 stateful · 2026-07-12 17:45:15 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,316,728 · 12 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
2w05w06w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8bc53a3…c2fe
0x34b655…2a6f
4 touches
1 conflict
0xe2c312f4…6eb6
0x34b655…2a6f
4 touches
1 conflict
0xf83b23f9…5a2e
0x34b655…2a6f
4 touches
1 conflict
0xf83b23f9…5a2f
0x34b655…2a6f
4 touches
1 conflict
0x58f65aa1…8f98
0x34b655…2a6f
4 touches
1 conflict
0x59a54ff4…d21b
0x34b655…2a6f
4 touches
1 conflict
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x777c0352…4d8c
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 0xd8bc53a346…42c2fe
Audit this contract →
← previous block·next block →recent activity