← previous blocknext block →recent activity
Analyzing
Block #80,164,233
17 transactions · 11 stateful · 2026-06-09 14:23:29 UTC
Parallelism
88/100
Blocked
9%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,164,233 · 17 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
13w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1e4de02…07e9
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xeb7e9d14…3ded
0x34b655…2a6f
4 touches
1 conflict
0x8210fa51…bc92
0x34b655…2a6f
4 touches
1 conflict
0x45e7e020…18aa
0x34b655…2a6f
4 touches
1 conflict
0x4b02a996…ee52
0x34b655…2a6f
2 touches
0 conflicts
0x7895a98c…bbfa
0x34b655…2a6f
2 touches
0 conflicts
0x908d4442…2c4b
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 0xd1e4de026f…2607e9
Audit this contract →
← previous block·next block →recent activity