← previous blocknext block →recent activity
Analyzing
Block #85,132,608
19 transactions · 18 stateful · 2026-07-02 14:45:36 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,132,608 · 19 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
1w03w04w05w19w112w114w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x6ca32a09…4e48
0x34b655…2a6f
6 touches
3 conflicts
0x06040b44…e244
0x34b655…2a6f
4 touches
1 conflict
0x31f93cf6…2786
0x34b655…2a6f
4 touches
1 conflict
0x366f651e…6100
0x34b655…2a6f
4 touches
1 conflict
0x6c78e3a8…2a3a
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7ae63663…9d94
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