← previous blocknext block →recent activity
Analyzing
Block #87,262,702
9 transactions · 7 stateful · 2026-07-12 11:44:03 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,262,702 · 9 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e859a7c…d0f2
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb3e53c5e…b99c
0x34b655…2a6f
4 touches
1 conflict
0xdc3d4f40…12c9
0x34b655…2a6f
4 touches
1 conflict
0xdd38f4e6…586c
0x34b655…2a6f
4 touches
1 conflict
0x619c81de…01b4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
2 touches
0 conflicts
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 0x6e859a7cbe…32d0f2
Audit this contract →
← previous block·next block →recent activity