← previous blocknext block →recent activity
Analyzing
Block #84,116,761
31 transactions · 25 stateful · 2026-06-27 21:51:59 UTC
Parallelism
84/100
Blocked
40%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,116,761 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w113w014w115w216w321w222w123w127w028w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2cdfa3f…f071
0x34b655…2a6f
10 touches
10 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
8 touches
6 conflicts
0xe02484a6…c32e
0xc8689a…ee79
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x19ce481d…6c36
0x34b655…2a6f
8 touches
6 conflicts
0x6f39323d…0dc6
0xd32edf…ff58
5 touches
3 conflicts
0xb1526c23…f2b9
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
10 conflicts on slot 0xd2cdfa3f93…37f071
Audit this contract →
← previous block·next block →recent activity