← previous blocknext block →recent activity
Analyzing
Block #98,663,826
31 transactions · 29 stateful · 2026-08-24 04:29:12 UTC
Parallelism
48/100
Blocked
66%
Avg conflicts / tx
4.1
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #98,663,826 · 31 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
2w04w15w26w312w013w114w215w316w417w518w619w720w821w922w1023w1124w1225w1326w1427w1529w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
32 touches
120 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x8c4d6783…4ae8
0x34b655…2a6f
4 touches
1 conflict
0x3cb7ee74…b8a5
0x34b655…2a6f
4 touches
1 conflict
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0x43a7dab1…7500
0x34b655…2a6f
4 touches
1 conflict
0xaf30c163…0fb6
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