← previous blocknext block →recent activity
Analyzing
Block #87,266,323
10 transactions · 9 stateful · 2026-07-12 12:08:12 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,266,323 · 10 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
1w03w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf44b5226…bf4e
0x34b655…2a6f
4 touches
1 conflict
0x256d690b…2bcb
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x4057827b…282c
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb251976b…4938
0x34b655…2a6f
4 touches
1 conflict
0xcbc71a55…aa9a
0x34b655…2a6f
4 touches
1 conflict
0xcbc71a55…aa9b
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 0xf44b522665…2abf4e
Audit this contract →
← previous block·next block →recent activity