← previous blocknext block →recent activity
Analyzing
Block #86,248,631
19 transactions · 17 stateful · 2026-07-07 18:44:30 UTC
Parallelism
89/100
Blocked
12%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,248,631 · 19 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
4w05w06w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e507257…71c1
0x34b655…2a6f
4 touches
1 conflict
0x1c796c6b…064e
0x34b655…2a6f
4 touches
1 conflict
0xdc8d4ee0…def3
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x181732de…9796
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x8e50725790…b871c1
Audit this contract →
← previous block·next block →recent activity