← previous blocknext block →recent activity
Analyzing
Block #86,315,346
21 transactions · 20 stateful · 2026-07-08 02:09:54 UTC
Parallelism
81/100
Blocked
45%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,315,346 · 21 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
2w04w05w16w29w310w112w114w215w317w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc588d2da…5cc8
0x34b655…2a6f
6 touches
3 conflicts
0xd1a8b9bd…6f8c
0x34b655…2a6f
6 touches
3 conflicts
0xd4726587…6289
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0xccdc4bad…55ad
0x851145…3f07
6 touches
3 conflicts
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 0xc588d2dadd…2e5cc8
Audit this contract →
← previous block·next block →recent activity