← previous blocknext block →recent activity
Analyzing
Block #85,937,720
8 transactions · 6 stateful · 2026-07-06 08:08:48 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,937,720 · 8 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
1w02w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63ce81c4…c889
0x34b655…2a6f
6 touches
3 conflicts
0xa15aa6b2…1626
0x34b655…2a6f
4 touches
1 conflict
0xa20a130c…5d59
0x34b655…2a6f
4 touches
1 conflict
0xa7396f51…7f2f
0x34b655…2a6f
4 touches
1 conflict
0xb9e57458…f6d8
0x34b655…2a6f
4 touches
1 conflict
0x97c67486…27fe
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6bd79c06…6d09
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 0x63ce81c4dc…e6c889
Audit this contract →
← previous block·next block →recent activity