← previous blocknext block →recent activity
Analyzing
Block #80,760,909
13 transactions · 12 stateful · 2026-06-12 08:42:18 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,760,909 · 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
1w02w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16dcea2f…25e6
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x001aaba1…c303
0x40c49f…2af0
2 touches
0 conflicts
0x2dbc1f0a…3f0d
0x40c49f…2af0
2 touches
0 conflicts
0x4d9f25f8…80cd
0x40c49f…2af0
2 touches
0 conflicts
0xbd3a9704…a155
0x40c49f…2af0
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 0x16dcea2fe5…b525e6
Audit this contract →
← previous block·next block →recent activity