← previous blocknext block →recent activity
Analyzing
Block #85,960,889
19 transactions · 16 stateful · 2026-07-06 10:43:19 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,960,889 · 19 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
1w02w18w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d34cc12…59a6
0x34b655…2a6f
4 touches
1 conflict
0xbbd4318b…a505
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x31616f97…1acc
0x34b655…2a6f
4 touches
1 conflict
0x3ecb52bd…1df6
0x0cc02c…75b2
2 touches
0 conflicts
0x40c0484d…8192
0x188d58…ea8e
2 touches
0 conflicts
0x40c0484d…8194
0x188d58…ea8e
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 0x9d34cc12c2…0b59a6
Audit this contract →
← previous block·next block →recent activity