← previous blocknext block →recent activity
Analyzing
Block #86,910,548
20 transactions · 18 stateful · 2026-07-10 20:29:58 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.2
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,910,548 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w113w214w019w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60927e35…2757
0x34b655…2a6f
4 touches
1 conflict
0x07d94be1…7fa8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x1941b441…5889
0x34b655…2a6f
4 touches
1 conflict
0x3a192eef…3c7f
0x34b655…2a6f
2 touches
0 conflicts
0x42150c2e…a526
0x34b655…2a6f
2 touches
0 conflicts
0x5a19ef35…dc70
0x34b655…2a6f
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 0x60927e35f8…422757
Audit this contract →
← previous block·next block →recent activity