← previous blocknext block →recent activity
Analyzing
Block #116,082,530
18 transactions · 14 stateful · 2026-10-24 04:00:42 UTC
Parallelism
78/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #116,082,530 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w07w111w012w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba0fd3cf…a6cc
0x34b655…2a6f
8 touches
6 conflicts
0x2d2fe283…1343
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0xed59b1cd…8509
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0x1bee5aea…5f61
0x34b655…2a6f
4 touches
1 conflict
0x23253ea8…e0a4
0x34b655…2a6f
4 touches
1 conflict
0x30951905…2da4
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
6 conflicts on slot 0xba0fd3cf0b…1ea6cc
Audit this contract →
← previous block·next block →recent activity