← previous blocknext block →recent activity
Analyzing
Block #86,958,829
22 transactions · 19 stateful · 2026-07-11 01:52:31 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,958,829 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w09w112w214w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee4fe1f7…3ead
0x34b655…2a6f
6 touches
3 conflicts
0x27a04273…27c5
0x065c9d…c394
4 touches
1 conflict
0x49cbdb1b…bda4
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x1eb0fab5…3517
0x34b655…2a6f
4 touches
1 conflict
0x28387633…e029
0x34b655…2a6f
4 touches
1 conflict
0x37748cc4…b8c7
0x34b655…2a6f
4 touches
1 conflict
0x3d2e2179…a584
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
3 conflicts on slot 0xee4fe1f73e…483ead
Audit this contract →
← previous block·next block →recent activity