← previous blocknext block →recent activity
Analyzing
Block #100,893,750
5 transactions · 5 stateful · 2026-09-01 00:01:45 UTC
Parallelism
60/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,893,750 · 5 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
0x420c4a20…aa5f
0x754704…b603
4 touches
1 conflict
0x7805c8f7…1376
0x754704…b603
4 touches
1 conflict
0x2f39c90b…19c8
0x99c7a7…8bf0
4 touches
1 conflict
0xa70f44db…0d08
0x99c7a7…8bf0
4 touches
1 conflict
0x06a8b17c…46e5
0x754704…b603
4 touches
1 conflict
0x037849a8…fa88
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad05
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad07
0x34b655…2a6f
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 0x420c4a20e7…a4aa5f
Audit this contract →
← previous block·next block →recent activity