← previous blocknext block →recent activity
Analyzing
Block #99,880,545
30 transactions · 28 stateful · 2026-08-28 10:58:28 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,880,545 · 30 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
2w03w04w15w16w210w211w116w017w018w119w320w221w422w523w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x165dc7e9…f4b1
0x34b655…2a6f
8 touches
6 conflicts
0x733c7779…a647
0x34b655…2a6f
8 touches
6 conflicts
0xadce6355…03bf
0xa6afd3…d132
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x6324ccc9…14fd
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
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
6 conflicts on slot 0x165dc7e9f0…bbf4b1
Audit this contract →
← previous block·next block →recent activity