← previous blocknext block →recent activity
Analyzing
Block #86,260,445
15 transactions · 14 stateful · 2026-07-07 20:03:25 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,260,445 · 15 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
1w02w14w05w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x159cff26…7665
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf788c790…e66f
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x3afc28a2…f138
0x40c49f…2af0
2 touches
0 conflicts
0x6cc1a133…89a0
0x40c49f…2af0
2 touches
0 conflicts
0xa1c77f83…246c
0x40c49f…2af0
2 touches
0 conflicts
0xb1bdf54a…e244
0x40c49f…2af0
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 0x159cff262c…e57665
Audit this contract →
← previous block·next block →recent activity