← previous blocknext block →recent activity
Analyzing
Block #80,240,617
18 transactions · 16 stateful · 2026-06-09 22:52:57 UTC
Parallelism
89/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,240,617 · 18 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
1w03w04w15w06w17w08w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0xebda062f…e87a
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x100024f3…9768
0x40c49f…2af0
3 touches
1 conflict
0xea038f5c…f4ab
0x065c9d…c394
3 touches
1 conflict
0xc98ea0dc…4eba
0x40c49f…2af0
2 touches
0 conflicts
0xd9144088…fb72
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 0x90f07a4ff9…b3d932
Audit this contract →
← previous block·next block →recent activity