← previous blocknext block →recent activity
Analyzing
Block #101,250,928
16 transactions · 16 stateful · 2026-09-02 05:58:57 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,250,928 · 16 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
3w04w15w06w17w28w09w110w211w312w413w515w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
12 touches
15 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xa6464996…3af9
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe2c4da1c…0e41
0x34b655…2a6f
4 touches
1 conflict
0xe2c4da1c…0e42
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)
15 conflicts on slot 0xd17580f913…78ece1
Audit this contract →
← previous block·next block →recent activity