← previous blocknext block →recent activity
Analyzing
Block #99,948,630
23 transactions · 23 stateful · 2026-08-28 16:41:37 UTC
Parallelism
87/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,948,630 · 23 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
1w02w13w06w08w09w110w111w214w016w217w118w219w220w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7668c61…55f8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x5a548af5…0eb0
0x34b655…2a6f
6 touches
3 conflicts
0xccd9466b…c821
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c0
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
3 conflicts on slot 0xd7668c6147…2355f8
Audit this contract →
← previous block·next block →recent activity