← previous blocknext block →recent activity
Analyzing
Block #80,631,346
15 transactions · 10 stateful · 2026-06-11 18:18:30 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,631,346 · 15 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
2w04w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4efae872…6aa8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfddc28be…e776
0x34b655…2a6f
4 touches
1 conflict
0x00ddbbf2…4588
0x34b655…2a6f
4 touches
1 conflict
0xef65bff3…7c9d
0x2a68ba…90c5
2 touches
0 conflicts
0x09f1a7b0…09b2
0x34b655…2a6f
2 touches
0 conflicts
0x0f82dba2…24d6
0x34b655…2a6f
2 touches
0 conflicts
0x40970e69…da50
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: Perpl
1 conflict on slot 0x4efae87285…886aa8
Audit this contract →
← previous block·next block →recent activity