← previous blocknext block →recent activity
Analyzing
Block #86,152,134
15 transactions · 13 stateful · 2026-07-07 08:00:05 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,152,134 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w07w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
10 touches
10 conflicts
0x1aaf4996…65ec
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x663d3288…f460
0x34b655…2a6f
4 touches
1 conflict
0x792e8ef7…5f52
0x34b655…2a6f
4 touches
1 conflict
0x92ddf0ac…8fa0
0x34b655…2a6f
4 touches
1 conflict
0x94dabb65…43a3
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
15 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity