← previous blocknext block →recent activity
Analyzing
Block #86,624,206
11 transactions · 11 stateful · 2026-07-09 12:35:24 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,624,206 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x272e5bd6…252d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb1f0701d…4f4a
0xc8689a…ee79
4 touches
1 conflict
0x1b60b708…5b4b
0x69df8a…6292
3 touches
1 conflict
0xa0971b70…8185
0x065c9d…c394
3 touches
1 conflict
0x2c69c53a…c0c7
0x065c9d…c394
2 touches
1 conflict
0x2c69c53a…c0c8
0x065c9d…c394
2 touches
1 conflict
0x9667d19e…4b12
0x69df8a…6292
2 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
1 conflict on slot 0x272e5bd6fd…dd252d
Audit this contract →
← previous block·next block →recent activity