← previous blocknext block →recent activity
Analyzing
Block #84,362,182
29 transactions · 24 stateful · 2026-06-29 01:06:54 UTC
Parallelism
76/100
Blocked
63%
Avg conflicts / tx
1.45
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,362,182 · 29 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w17w28w09w110w011w112w213w314w415w516w619w520w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x8fcf2308…746e
0x34b655…2a6f
12 touches
15 conflicts
0x753da1ce…6bbd
0x34b655…2a6f
10 touches
10 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
10 touches
10 conflicts
0xcffc17bc…3544
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity