← previous blocknext block →recent activity
Analyzing
Block #85,601,989
25 transactions · 23 stateful · 2026-07-04 18:51:40 UTC
Parallelism
88/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,601,989 · 25 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
17w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00966e54…7d1d
0x34b655…2a6f
4 touches
1 conflict
0x01414ad2…98ec
0x34b655…2a6f
4 touches
1 conflict
0x0ad4dbe8…ae93
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x178db37f…debb
0x34b655…2a6f
4 touches
1 conflict
0x1c91542b…f7b1
0x34b655…2a6f
4 touches
1 conflict
0x3c331367…0dbf
0x34b655…2a6f
4 touches
1 conflict
0x42bf88c1…c8d4
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
1 conflict on slot 0x00966e5492…9a7d1d
Audit this contract →
← previous block·next block →recent activity