← previous blocknext block →recent activity
Analyzing
Block #98,263,832
27 transactions · 24 stateful · 2026-08-22 18:26:21 UTC
Parallelism
93/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,263,832 · 27 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
2w05w013w116w017w126w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x1d10f24a…2fb8
0xa6afd3…d132
4 touches
1 conflict
0x71717491…10cf
0xa6afd3…d132
4 touches
1 conflict
0xc45e4fb5…7cc3
0xa6afd3…d132
4 touches
1 conflict
0xbb348e7e…f385
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x057c6242…da7e
0x34b655…2a6f
4 touches
1 conflict
0xd4c946a4…b8d4
0x754704…b603
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: Kuru Exchange: Market-WETH/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity