← previous blocknext block →recent activity
Analyzing
Block #86,837,820
14 transactions · 11 stateful · 2026-07-10 12:23:39 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,837,820 · 14 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
2w03w14w05w26w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x574c00dc…ea38
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x961c0cd9…0937
0x34b655…2a6f
4 touches
1 conflict
0xc2d989c0…8523
0x34b655…2a6f
4 touches
1 conflict
0xe1a1a29a…a399
0x34b655…2a6f
4 touches
1 conflict
0x574c00dc…ea37
0x34b655…2a6f
4 touches
1 conflict
0x3483ab79…8ed3
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 0x574c00dc09…d1ea38
Audit this contract →
← previous block·next block →recent activity