← previous blocknext block →recent activity
Analyzing
Block #87,284,069
11 transactions · 6 stateful · 2026-07-12 14:06:54 UTC
Parallelism
82/100
Blocked
17%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,284,069 · 11 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcbe18c62…3a5d
0x34b655…2a6f
4 touches
1 conflict
0xcbe18c62…3a5c
0x34b655…2a6f
4 touches
1 conflict
0x034d14da…9f5f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa55aabd7…cdfd
0x34b655…2a6f
4 touches
1 conflict
0x20822335…a26d
0x34b655…2a6f
3 touches
1 conflict
0x44231245…5442
0x34b655…2a6f
3 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 0xcbe18c620b…303a5d
Audit this contract →
← previous block·next block →recent activity