← previous blocknext block →recent activity
Analyzing
Block #85,362,587
20 transactions · 19 stateful · 2026-07-03 16:17:27 UTC
Parallelism
70/100
Blocked
37%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,362,587 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w28w012w213w314w415w018w519w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xfda82828…72de
0x34b655…2a6f
6 touches
3 conflicts
0xa20a130c…5d59
0x34b655…2a6f
6 touches
3 conflicts
0xca111140…2c7a
0x34b655…2a6f
6 touches
3 conflicts
0xda2ee2e7…968a
0x34b655…2a6f
6 touches
3 conflicts
0xdc746738…0698
0x34b655…2a6f
6 touches
3 conflicts
0x68c07cb9…ae14
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity