← previous blocknext block →recent activity
Analyzing
Block #85,194,093
8 transactions · 8 stateful · 2026-07-02 21:35:06 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,194,093 · 8 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
4w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x833ebd97…5abb
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xf081b45b…c7a5
0x34b655…2a6f
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
2 touches
0 conflicts
0xe34ad099…c630
0x065c9d…c394
2 touches
0 conflicts
0xf8a2ab67…0efb
0x065c9d…c394
2 touches
0 conflicts
0xfacc9ebd…065c
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 0x833ebd9703…2b5abb
Audit this contract →
← previous block·next block →recent activity