← previous blocknext block →recent activity
Analyzing
Block #84,029,196
13 transactions · 10 stateful · 2026-06-27 12:08:42 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,029,196 · 13 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
6w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86b6849c…08d4
0x34b655…2a6f
4 touches
1 conflict
0x5e03a380…a551
0x34b655…2a6f
4 touches
1 conflict
0xa0c6e179…a103
0x34b655…2a6f
4 touches
1 conflict
0x73ca2093…8dd6
0x34b655…2a6f
3 touches
1 conflict
0x21775316…927c
0x34b655…2a6f
2 touches
0 conflicts
0x5dc2541c…dd2f
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
0x34b655…2a6f
2 touches
0 conflicts
0x89c2fc95…3b05
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 0x86b6849c5c…8f08d4
Audit this contract →
← previous block·next block →recent activity