← previous blocknext block →recent activity
Analyzing
Block #86,978,616
18 transactions · 17 stateful · 2026-07-11 04:04:42 UTC
Parallelism
83/100
Blocked
24%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,978,616 · 18 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
3w04w16w27w011w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe59df86b…a00c
0x34b655…2a6f
4 touches
1 conflict
0xed660153…a905
0x34b655…2a6f
4 touches
1 conflict
0xfe8aac6e…6594
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x64800813…db9f
0x34b655…2a6f
4 touches
1 conflict
0x730a64b9…1b00
0x34b655…2a6f
4 touches
1 conflict
0x7561f24a…4522
0x34b655…2a6f
4 touches
1 conflict
0x75959b84…9bda
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 0xe59df86ba4…a3a00c
Audit this contract →
← previous block·next block →recent activity