← previous blocknext block →recent activity
Analyzing
Block #80,625,048
27 transactions · 18 stateful · 2026-06-11 17:36:29 UTC
Parallelism
89/100
Blocked
28%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,625,048 · 27 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w18w09w110w217w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb18bf8…e9f3
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xb3eae1cb…7249
0x1111b3…4111
2 touches
0 conflicts
0x5ff3595c…a5a0
0x754704…b603
2 touches
0 conflicts
0x972647de…0759
0x754704…b603
2 touches
0 conflicts
0xa1087a5c…66c4
0x754704…b603
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: 0xb18bf8fc…77e9f3
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity