← previous blocknext block →recent activity
Analyzing
Block #87,317,329
9 transactions · 8 stateful · 2026-07-12 17:49:16 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,317,329 · 9 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
2w04w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc94dfe1…0b3d
0x34b655…2a6f
6 touches
3 conflicts
0xebeee24a…ed8d
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x94ba9c4a…41d8
0x34b655…2a6f
4 touches
1 conflict
0xb35e663e…354e
0x34b655…2a6f
4 touches
1 conflict
0xc8d31c56…91df
0x34b655…2a6f
4 touches
1 conflict
0xd2171a4a…a036
0x34b655…2a6f
4 touches
1 conflict
0xe2c312f4…6eb6
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 0xbc94dfe1d8…a70b3d
Audit this contract →
← previous block·next block →recent activity