← previous blocknext block →recent activity
Analyzing
Block #84,594,695
11 transactions · 9 stateful · 2026-06-30 02:57:31 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,594,695 · 11 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
4w06w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f93f2f0…6666
0x34b655…2a6f
4 touches
1 conflict
0xd0806a61…8350
0x34b655…2a6f
4 touches
1 conflict
0xf98f45fd…37b1
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x1a6aa811…d425
0x34b655…2a6f
2 touches
0 conflicts
0x1c483719…720b
0x34b655…2a6f
2 touches
0 conflicts
0x1ca5aec6…c1e1
0x34b655…2a6f
2 touches
0 conflicts
0x2060d8b9…a088
0x34b655…2a6f
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 0x7f93f2f081…846666
Audit this contract →
← previous block·next block →recent activity