← previous blocknext block →recent activity
Analyzing
Block #98,655,893
35 transactions · 30 stateful · 2026-08-24 03:47:44 UTC
Parallelism
54/100
Blocked
67%
Avg conflicts / tx
3.6
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #98,655,893 · 35 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w09w010w113w214w115w016w117w018w119w220w321w422w523w624w725w826w927w1028w1129w1230w1331w1432w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
32 touches
120 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x11b69a7e…334e
0xee8c0e…1242
6 touches
3 conflicts
0xde44bbae…d98c
0xa6afd3…d132
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x89cacb6c…aff9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc4c059d8…185d
0x34b655…2a6f
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: USDC (USDC)
120 conflicts on slot 0xd17580f913…78ece1
Audit this contract →
← previous block·next block →recent activity