← previous blocknext block →recent activity
Analyzing
Block #80,286,804
13 transactions · 11 stateful · 2026-06-10 04:00:48 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,286,804 · 13 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
1w02w14w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb04d17a0…10e8
0x34b655…2a6f
8 touches
6 conflicts
0x1da1c6cb…bb3f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf5310ef7…485a
0x40c49f…2af0
4 touches
1 conflict
0x1454e171…a443
0x34b655…2a6f
4 touches
1 conflict
0xbf09519c…1bfe
0x34b655…2a6f
4 touches
1 conflict
0xfe39a1f7…8eb0
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 0xb04d17a0fe…4810e8
Audit this contract →
← previous block·next block →recent activity