← previous blocknext block →recent activity
Analyzing
Block #84,362,842
26 transactions · 19 stateful · 2026-06-29 01:11:18 UTC
Parallelism
81/100
Blocked
42%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,362,842 · 26 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
1w05w06w110w011w112w013w114w216w217w123w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c6984da…21e5
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x3f7ad3a0…de3b
0x34b655…2a6f
4 touches
1 conflict
0x948b9065…93b4
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xda7f9bd2…e332
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
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
3 conflicts on slot 0x7c6984da0c…7821e5
Audit this contract →
← previous block·next block →recent activity