← previous blocknext block →recent activity
Analyzing
Block #85,679,748
22 transactions · 17 stateful · 2026-07-05 03:29:11 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,679,748 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w18w210w014w015w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa457c06e…2f06
0x34b655…2a6f
6 touches
3 conflicts
0xb4aa41e0…f123
0x34b655…2a6f
6 touches
3 conflicts
0x9a573905…60cf
0x34b655…2a6f
6 touches
3 conflicts
0x4eedf1dd…8890
0x34b655…2a6f
4 touches
1 conflict
0x50fed00e…b35c
0x34b655…2a6f
4 touches
1 conflict
0x6bf8ab1e…5a19
0x34b655…2a6f
4 touches
1 conflict
0x805d08cf…3cfc
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