← previous blocknext block →recent activity
Analyzing
Block #100,734,469
13 transactions · 13 stateful · 2026-08-31 10:40:06 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,734,469 · 13 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02f4f6e2…47c6
0x754704…b603
4 touches
1 conflict
0x0449d018…e334
0x754704…b603
4 touches
1 conflict
0xe332b0a5…0bdb
0x754704…b603
4 touches
1 conflict
0x3b41d761…cd85
0x99c7a7…8bf0
4 touches
1 conflict
0xe10ff4f0…94b7
0x99c7a7…8bf0
4 touches
1 conflict
0x08d53462…97ef
0x34ae4d…3fc5
2 touches
0 conflicts
0x12f129f2…fe6b
0x34ae4d…3fc5
2 touches
0 conflicts
0x260cc5c4…bef0
0x34ae4d…3fc5
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: USDC (USDC)
1 conflict on slot 0x02f4f6e29d…5b47c6
Audit this contract →
← previous block·next block →recent activity