← previous blocknext block →recent activity
Analyzing
Block #86,360,811
16 transactions · 10 stateful · 2026-07-08 07:13:29 UTC
Parallelism
88/100
Blocked
30%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,360,811 · 16 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
1w02w16w07w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x5d537073…cf27
0x34b655…2a6f
4 touches
1 conflict
0x1ebe108b…72a0
0x34b655…2a6f
4 touches
1 conflict
0xba1cfb67…1bfe
0x34b655…2a6f
3 touches
1 conflict
0x94623194…97c1
0x34b655…2a6f
3 touches
1 conflict
0xc8ac9dce…df69
0xd32edf…ff58
3 touches
1 conflict
0x46cb45de…a566
0x188d58…ea8e
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 0xe06bbb2ef5…889416
Audit this contract →
← previous block·next block →recent activity