← previous blocknext block →recent activity
Analyzing
Block #80,276,112
19 transactions · 18 stateful · 2026-06-10 02:49:36 UTC
Parallelism
68/100
Blocked
33%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,276,112 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w110w012w114w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x085df2c1…305a
0x34b655…2a6f
6 touches
3 conflicts
0xd2a01381…4643
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x6b7e25db…9251
0x34b655…2a6f
4 touches
1 conflict
0x7c6d3d6d…9deb
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity