← previous blocknext block →recent activity
Analyzing
Block #101,248,117
20 transactions · 20 stateful · 2026-09-02 05:44:49 UTC
Parallelism
60/100
Blocked
65%
Avg conflicts / tx
1.8
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,248,117 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w06w07w18w09w110w211w312w413w514w615w717w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
16 touches
28 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x73912233…4585
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x16ebf93b…ce00
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)
28 conflicts on slot 0xd17580f913…78ece1
Audit this contract →
← previous block·next block →recent activity