← previous blocknext block →recent activity
Analyzing
Block #80,279,089
23 transactions · 17 stateful · 2026-06-10 03:09:28 UTC
Parallelism
91/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,279,089 · 23 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
1w02w18w09w010w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0x08943ea2…ed03
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e70
0x188d58…ea8e
2 touches
0 conflicts
0xf4a5a73e…c014
0x188d58…ea8e
2 touches
0 conflicts
0xf4a5a73e…c015
0x188d58…ea8e
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 0x90f07a4ff9…b3d932
Audit this contract →
← previous block·next block →recent activity