← previous blocknext block →recent activity
Analyzing
Block #86,298,801
14 transactions · 13 stateful · 2026-07-08 00:19:20 UTC
Parallelism
57/100
Blocked
54%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,298,801 · 14 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
2w03w14w26w27w08w39w112w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x7506443a…4820
0x34b655…2a6f
6 touches
3 conflicts
0x3a6290da…e683
0x34b655…2a6f
6 touches
3 conflicts
0xe21234e7…bded
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0xf5012b17…2996
0x34b655…2a6f
6 touches
3 conflicts
0xa57576bb…e01f
0x34b655…2a6f
6 touches
3 conflicts
0x3659eace…e64e
0x34b655…2a6f
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
6 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity