← previous blocknext block →recent activity
Analyzing
Block #84,564,149
15 transactions · 14 stateful · 2026-06-29 23:33:57 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.07
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,564,149 · 15 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
1w02w15w06w18w29w210w211w312w414w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98d58911…19f2
0x34b655…2a6f
8 touches
6 conflicts
0xa42e8482…b88f
0x34b655…2a6f
8 touches
6 conflicts
0xacb691b6…8e39
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x74888025…a5b8
0x34b655…2a6f
6 touches
3 conflicts
0x2c15adb7…e65d
0x34b655…2a6f
4 touches
1 conflict
0x374fc18a…6998
0x34b655…2a6f
4 touches
1 conflict
0x3891cd1c…e740
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
6 conflicts on slot 0x98d589117f…0c19f2
Audit this contract →
← previous block·next block →recent activity