← previous blocknext block →recent activity
Analyzing
Block #84,497,307
12 transactions · 11 stateful · 2026-06-29 16:07:43 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,497,307 · 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0xcdbbb43a…14b1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x1d6cb721…c88c
0x34b655…2a6f
2 touches
0 conflicts
0x1e04c5ec…8d51
0x34b655…2a6f
2 touches
0 conflicts
0x242bdfb5…974d
0x34b655…2a6f
2 touches
0 conflicts
0x32e09896…a1be
0x34b655…2a6f
2 touches
0 conflicts
0x39cc2185…caca
0x34b655…2a6f
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 0x6f132c01d5…7dcdcc
Audit this contract →
← previous block·next block →recent activity