← previous blocknext block →recent activity
Analyzing
Block #85,100,922
17 transactions · 14 stateful · 2026-07-02 11:13:22 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,100,922 · 17 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
1w03w16w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2406ccf7…c1cb
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
2 touches
0 conflicts
0x85f9b4be…4c67
0x065c9d…c394
2 touches
0 conflicts
0x90b40370…afa7
0x065c9d…c394
2 touches
0 conflicts
0x973a5394…14ab
0x065c9d…c394
2 touches
0 conflicts
0xec7c6fb5…0653
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 0x2406ccf7d1…d8c1cb
Audit this contract →
← previous block·next block →recent activity