← previous blocknext block →recent activity
Analyzing
Block #84,348,158
12 transactions · 12 stateful · 2026-06-28 23:33:18 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,348,158 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w08w19w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2cdfa3f…f071
0x34b655…2a6f
4 touches
1 conflict
0xa9db7b4d…2957
0x40c49f…2af0
4 touches
1 conflict
0xf5970b31…f34c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x2842be7f…84b8
0x40c49f…2af0
3 touches
1 conflict
0x84eea0a4…1dae
0x40c49f…2af0
3 touches
1 conflict
0xdfc5f346…7b42
0x40c49f…2af0
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
2 touches
0 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
1 conflict on slot 0xd2cdfa3f93…37f071
Audit this contract →
← previous block·next block →recent activity