← previous blocknext block →recent activity
Analyzing
Block #80,665,847
15 transactions · 14 stateful · 2026-06-11 22:08:25 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,665,847 · 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
1w02w13w211w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb182933f…46ed
0x754704…b603
2 touches
1 conflict
0x9d3f2124…725b
0x2a68ba…90c5
2 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x7570be2b…a7b4
0x065c9d…c394
2 touches
0 conflicts
0xa2b0c44e…90fa
0x065c9d…c394
2 touches
0 conflicts
0x22a828bf…8b10
0x5e0734…69c1
2 touches
0 conflicts
0x61c7a97a…5755
0x5e0734…69c1
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity