← previous blocknext block →recent activity
Analyzing
Block #84,489,596
23 transactions · 16 stateful · 2026-06-29 15:16:15 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,489,596 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w110w011w112w213w320w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd1a8b9bd…6f8c
0x34b655…2a6f
5 touches
3 conflicts
0x042c98e4…2c39
0x34b655…2a6f
4 touches
1 conflict
0x0833f1ab…71e7
0x34b655…2a6f
4 touches
1 conflict
0x0b408000…9df1
0x34b655…2a6f
4 touches
1 conflict
0x1ab9142a…2cfd
0x34b655…2a6f
4 touches
1 conflict
0x206f4379…e08a
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity