← previous blocknext block →recent activity
Analyzing
Block #80,743,342
147 transactions · 17 stateful · 2026-06-12 06:45:10 UTC
Parallelism
96/100
Blocked
41%
Avg conflicts / tx
0.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,743,342 · 147 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
1w02w141w061w182w297w3111w4123w5138w0139w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e5cc690…b06b
0x34b655…2a6f
10 touches
10 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
10 touches
10 conflicts
0xf6476f21…3580
0x34b655…2a6f
8 touches
6 conflicts
0x60ad7285…2ca5
0x34b655…2a6f
4 touches
1 conflict
0x6d94d7d6…6ed4
0x34b655…2a6f
4 touches
1 conflict
0x781f5487…d318
0x34b655…2a6f
4 touches
1 conflict
0x7938c6fd…1cd1
0x34b655…2a6f
4 touches
1 conflict
0xa3ff1ab2…8ae3
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 0x8e5cc69035…0db06b
Audit this contract →
← previous block·next block →recent activity