← previous blocknext block →recent activity
Analyzing
Block #86,447,343
18 transactions · 18 stateful · 2026-07-08 16:51:40 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,447,343 · 18 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
6w010w111w212w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0622e090…8fc5
0x34b655…2a6f
4 touches
1 conflict
0xb31b567f…387f
0x34b655…2a6f
4 touches
1 conflict
0xc5a1b2fe…5369
0x34b655…2a6f
4 touches
1 conflict
0x555c4fd7…ae1a
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x7506443a…4820
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 0x0622e090c5…0d8fc5
Audit this contract →
← previous block·next block →recent activity