← previous blocknext block →recent activity
Analyzing
Block #80,600,246
16 transactions · 12 stateful · 2026-06-11 14:50:43 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,600,246 · 16 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
1w02w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57efb579…dd5c
0x40c49f…2af0
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x342fbbca…d443
0x40c49f…2af0
4 touches
1 conflict
0x622ad0d4…4b42
0x065c9d…c394
2 touches
0 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
2 touches
0 conflicts
0x213ee207…a151
0x69df8a…6292
2 touches
0 conflicts
0x45f562b2…9294
0x69df8a…6292
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: 0x40c49f17…d22af0
1 conflict on slot 0x57efb5798c…2ddd5c
Audit this contract →
← previous block·next block →recent activity