← previous blocknext block →recent activity
Analyzing
Block #80,166,412
16 transactions · 11 stateful · 2026-06-09 14:38:01 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,166,412 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w07w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xcb496cdb…b731
0x065c9d…c394
3 touches
1 conflict
0x00000000…0070
0x1efe02…37d6
2 touches
0 conflicts
0x04a0303d…ca3b
0x1efe02…37d6
2 touches
0 conflicts
0x3b2f0b0b…cd05
0x1efe02…37d6
2 touches
0 conflicts
0x71729695…12ca
0x1efe02…37d6
2 touches
0 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity