← previous blocknext block →recent activity
Analyzing
Block #86,105,135
11 transactions · 9 stateful · 2026-07-07 02:46:18 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,105,135 · 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
1w02w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5eb3c33…0e3a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0991fdda…a745
0x2ab50b…5c41
2 touches
0 conflicts
0x1449b49f…d1d8
0x2ab50b…5c41
2 touches
0 conflicts
0x15a8b5e6…0296
0x2ab50b…5c41
2 touches
0 conflicts
0x1fa8caa1…fa41
0x2ab50b…5c41
2 touches
0 conflicts
0x2d8cbe70…2ffb
0x2ab50b…5c41
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 0xe5eb3c3335…0c0e3a
Audit this contract →
← previous block·next block →recent activity