← previous blocknext block →recent activity
Analyzing
Block #84,513,137
28 transactions · 20 stateful · 2026-06-29 17:53:21 UTC
Parallelism
82/100
Blocked
45%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,513,137 · 28 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
1w04w15w27w211w012w113w214w316w017w118w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xacbc3fbb…fe8e
0x34b655…2a6f
10 touches
10 conflicts
0xe02484a6…c32e
0xc8689a…ee79
8 touches
6 conflicts
0x3766925b…76fe
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x49b0842d…0a93
0x34b655…2a6f
8 touches
6 conflicts
0x41513008…b322
0x34b655…2a6f
6 touches
3 conflicts
0xe41f8863…29a4
0xa6afd3…d132
6 touches
3 conflicts
0x5a19ef35…dc70
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xacbc3fbbbb…75fe8e
Audit this contract →
← previous block·next block →recent activity