← previous blocknext block →recent activity
Analyzing
Block #84,493,411
28 transactions · 22 stateful · 2026-06-29 15:41:44 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
0.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,493,411 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w110w011w112w213w314w419w523w224w226w627w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
6 touches
3 conflicts
0x2754e960…bcc1
0x34b655…2a6f
6 touches
3 conflicts
0x83f3d320…fb59
0x34b655…2a6f
6 touches
3 conflicts
0x8e739938…e7ab
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc94da5de…7ca7
0x34b655…2a6f
6 touches
3 conflicts
0x29633a56…3007
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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity