← previous blocknext block →recent activity
Analyzing
Block #87,712,267
22 transactions · 20 stateful · 2026-07-14 13:51:12 UTC
Parallelism
86/100
Blocked
40%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,712,267 · 22 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
2w03w14w05w16w07w110w113w114w115w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x389a56a6…986f
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x199944d5…ab9f
0x34b655…2a6f
4 touches
1 conflict
0x6c2aa5be…d808
0x34b655…2a6f
4 touches
1 conflict
0x6e859a7c…d0f2
0x34b655…2a6f
4 touches
1 conflict
0x722851f4…73fe
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: 0x40c49f17…d22af0
1 conflict on slot 0x389a56a69a…86986f
Audit this contract →
← previous block·next block →recent activity