← previous blocknext block →recent activity
Analyzing
Block #100,700,583
13 transactions · 13 stateful · 2026-08-31 07:49:38 UTC
Parallelism
62/100
Blocked
46%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,700,583 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w49w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x65021fef…b735
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0xabde8104…c9a9
0x2a68ba…90c5
2 touches
0 conflicts
0x06e40499…165e
0x34ae4d…3fc5
2 touches
0 conflicts
0x10d80fee…dbda
0x34ae4d…3fc5
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: USDC (USDC)
10 conflicts on slot 0xd17580f913…78ece1
Audit this contract →
← previous block·next block →recent activity