← previous blocknext block →recent activity
Analyzing
Block #86,532,013
18 transactions · 17 stateful · 2026-07-09 02:17:24 UTC
Parallelism
89/100
Blocked
24%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,532,013 · 18 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
1w02w13w04w16w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19b8ee99…c08a
0x34b655…2a6f
4 touches
1 conflict
0x1cc39c91…f518
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x44429a9b…771d
0x34b655…2a6f
4 touches
1 conflict
0x58adb371…0d3a
0x34b655…2a6f
4 touches
1 conflict
0x8ae6d2fe…66f4
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x9138a113…0d5f
0x34b655…2a6f
4 touches
1 conflict
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 0x19b8ee994c…cac08a
Audit this contract →
← previous block·next block →recent activity