← previous blocknext block →recent activity
Analyzing
Block #85,788,105
24 transactions · 19 stateful · 2026-07-05 15:32:01 UTC
Parallelism
79/100
Blocked
37%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,788,105 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w18w19w010w116w117w218w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc7f7d98f…cfe7
0x34b655…2a6f
8 touches
6 conflicts
0x64c57c87…5e42
0x34b655…2a6f
6 touches
3 conflicts
0x2b510939…3187
0x34b655…2a6f
6 touches
3 conflicts
0x18de899b…7b35
0x34b655…2a6f
4 touches
1 conflict
0x2c7ab45b…62bd
0x34b655…2a6f
4 touches
1 conflict
0x757b0543…e087
0x34b655…2a6f
4 touches
1 conflict
0x7a2fc410…c088
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