← previous blocknext block →recent activity
Analyzing
Block #86,074,367
30 transactions · 26 stateful · 2026-07-06 23:21:08 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,074,367 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w07w18w29w015w119w123w024w125w226w327w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x0a1442e4…6504
0x065c9d…c394
4 touches
1 conflict
0x11560115…bfc2
0x34b655…2a6f
4 touches
1 conflict
0x6f58168d…ea24
0x34b655…2a6f
4 touches
1 conflict
0x73133f6f…0711
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity