← previous blocknext block →recent activity
Analyzing
Block #85,502,432
19 transactions · 14 stateful · 2026-07-04 07:48:40 UTC
Parallelism
74/100
Blocked
43%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,502,432 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w07w111w112w114w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xafb2524a…0ce4
0x34b655…2a6f
6 touches
3 conflicts
0xc8304415…4f91
0x34b655…2a6f
6 touches
3 conflicts
0x1ab62a3e…f6cb
0x34b655…2a6f
4 touches
1 conflict
0x2f9754df…5239
0x34b655…2a6f
4 touches
1 conflict
0x3e585dfe…76b4
0x34b655…2a6f
4 touches
1 conflict
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x503b3a72…f6df
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity