← previous blocknext block →recent activity
Analyzing
Block #80,310,325
16 transactions · 11 stateful · 2026-06-10 06:37:41 UTC
Parallelism
81/100
Blocked
18%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,310,325 · 16 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
5w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe3d37ee…6e67
0x34b655…2a6f
4 touches
1 conflict
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0a4735f0…ce6a
0x3bd359…433a
2 touches
0 conflicts
0x43a86fb8…e9c9
0x3bd359…433a
2 touches
0 conflicts
0xfe3bddd2…8b48
0x3bd359…433a
2 touches
0 conflicts
0x689eb39b…c67e
0x740d1d…373c
2 touches
0 conflicts
0x788e1e27…26ce
0x740d1d…373c
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 0xfe3d37ee7e…836e67
Audit this contract →
← previous block·next block →recent activity