← previous blocknext block →recent activity
Analyzing
Block #85,158,902
12 transactions · 11 stateful · 2026-07-02 17:40:51 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,158,902 · 12 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
4w05w18w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x6f58168d…ea24
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0xc08384da…ecb7
0x34b655…2a6f
4 touches
1 conflict
0x0ad4dbe8…ae93
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0x5138188e…796b
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