← previous blocknext block →recent activity
Analyzing
Block #84,510,131
17 transactions · 17 stateful · 2026-06-29 17:33:18 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,510,131 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w28w39w410w115w016w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6e11b8f…f12b
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xe4afaa2f…3b69
0xa6afd3…d132
4 touches
1 conflict
0x0388b940…f9e1
0x34b655…2a6f
4 touches
1 conflict
0x178fe051…465a
0x34b655…2a6f
4 touches
1 conflict
0x2328941c…84d3
0x34b655…2a6f
4 touches
1 conflict
0x7c6d3d6d…9deb
0x34b655…2a6f
4 touches
1 conflict
0xb31b567f…387f
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
3 conflicts on slot 0xb6e11b8f54…5df12b
Audit this contract →
← previous block·next block →recent activity