← previous blocknext block →recent activity
Analyzing
Block #86,766,532
10 transactions · 8 stateful · 2026-07-10 04:27:14 UTC
Parallelism
70/100
Blocked
63%
Avg conflicts / tx
0.8
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,766,532 · 10 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
1w02w14w05w16w17w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c2e78a1…2f95
0x34b655…2a6f
6 touches
3 conflicts
0x0bc5d643…38d8
0x34b655…2a6f
4 touches
1 conflict
0x0bc5d643…38d9
0x34b655…2a6f
4 touches
1 conflict
0x1cd6787c…8a13
0x34b655…2a6f
4 touches
1 conflict
0x1d826725…e975
0x34b655…2a6f
4 touches
1 conflict
0x1ffe7d94…61ea
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49a97bff…33ed
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 0x4c2e78a102…002f95
Audit this contract →
← previous block·next block →recent activity