← previous blocknext block →recent activity
Analyzing
Block #80,164,246
25 transactions · 17 stateful · 2026-06-09 14:23:34 UTC
Parallelism
84/100
Blocked
53%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,164,246 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w16w27w18w210w011w112w213w317w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x36d366fe…7adc
0xa6afd3…d132
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x0e5f2a94…4732
0x34b655…2a6f
4 touches
1 conflict
0x4b02a996…ee52
0x34b655…2a6f
4 touches
1 conflict
0x7895a98c…bbfa
0x34b655…2a6f
4 touches
1 conflict
0x8db1e0f2…2fcf
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x90f07a4ff9…b3d932
Audit this contract →
← previous block·next block →recent activity