← previous blocknext block →recent activity
Analyzing
Block #85,104,055
19 transactions · 12 stateful · 2026-07-02 11:34:31 UTC
Parallelism
89/100
Blocked
8%
Avg conflicts / tx
0.05
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,104,055 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
16w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0a4133e…6110
0x34b655…2a6f
4 touches
1 conflict
0xd27d3461…72b1
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b77eb22…64ec
0x065c9d…c394
2 touches
0 conflicts
0x19d6f4fc…bee2
0x065c9d…c394
2 touches
0 conflicts
0x2cc529a7…1ac0
0x065c9d…c394
2 touches
0 conflicts
0x59ab478d…ab78
0x065c9d…c394
2 touches
0 conflicts
0x731e6d82…2883
0x065c9d…c394
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 0xc0a4133ed0…a76110
Audit this contract →
← previous block·next block →recent activity