← previous blocknext block →recent activity
Analyzing
Block #86,661,020
16 transactions · 13 stateful · 2026-07-09 16:42:39 UTC
Parallelism
81/100
Blocked
46%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,661,020 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w17w210w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6805ef8…e22e
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x2d7ea048…d78e
0x34b655…2a6f
4 touches
1 conflict
0x3592ddbc…334f
0x34b655…2a6f
4 touches
1 conflict
0x3d2b954a…8b7a
0x34b655…2a6f
4 touches
1 conflict
0x4242b051…aa68
0x34b655…2a6f
4 touches
1 conflict
0x485ae99d…f26f
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
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
3 conflicts on slot 0xe6805ef89e…4fe22e
Audit this contract →
← previous block·next block →recent activity