← previous blocknext block →recent activity
Analyzing
Block #85,988,621
16 transactions · 11 stateful · 2026-07-06 13:48:30 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,988,621 · 16 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
1w02w15w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0xd244ddb7…57b8
0x34b655…2a6f
4 touches
1 conflict
0xd90a674b…29f7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x5f63a7ef…23bb
0x40c49f…2af0
2 touches
0 conflicts
0xd16df6cd…5532
0x40c49f…2af0
2 touches
0 conflicts
0xf5310ef7…485a
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 0x4a5956ef63…f0e226
Audit this contract →
← previous block·next block →recent activity