← previous blocknext block →recent activity
Analyzing
Block #100,892,332
10 transactions · 9 stateful · 2026-08-31 23:54:37 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,892,332 · 10 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
1w02w15w06w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6658fa82…4017
0x754704…b603
4 touches
1 conflict
0xf371c34e…e4ac
0x754704…b603
4 touches
1 conflict
0x266a6b2c…4376
0x34b655…2a6f
4 touches
1 conflict
0x266a6b2c…4377
0x34b655…2a6f
4 touches
1 conflict
0x3bdcc58a…a1b1
0x99c7a7…8bf0
4 touches
1 conflict
0x66d9a0d3…b98c
0x99c7a7…8bf0
4 touches
1 conflict
0x46abeefb…fc9c
0x34b655…2a6f
4 touches
1 conflict
0xa453491f…c515
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)
1 conflict on slot 0x6658fa8255…c84017
Audit this contract →
← previous block·next block →recent activity