← previous blocknext block →recent activity
Analyzing
Block #99,871,306
37 transactions · 34 stateful · 2026-08-28 10:11:56 UTC
Parallelism
84/100
Blocked
59%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,871,306 · 37 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
1w02w03w14w15w06w28w09w110w011w112w113w014w116w118w020w125w226w327w433w234w336w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0xb31eb7d3…64eb
0xa6afd3…d132
8 touches
6 conflicts
0xc21def1b…c24d
0xa6afd3…d132
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x359866c7…de7b
0x34b655…2a6f
6 touches
3 conflicts
0xcf61f287…3f4e
0x34b655…2a6f
6 touches
3 conflicts
0xe7ad475a…0e41
0x34b655…2a6f
6 touches
3 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: Kuru Exchange: Market-WETH/USDC
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity