← previous blocknext block →recent activity
Analyzing
Block #106,959,608
17 transactions · 17 stateful · 2026-09-22 06:07:46 UTC
Parallelism
88/100
Blocked
24%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,959,608 · 17 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
1w02w16w07w08w110w011w113w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a7e4e98…1f3b
0x754704…b603
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0xd4c946a4…b8d4
0x754704…b603
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x363d5ac3…a29d
0x99c7a7…8bf0
4 touches
1 conflict
0x628e0d85…2e5c
0x99c7a7…8bf0
4 touches
1 conflict
0xd98b3c10…67b8
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 0x5a7e4e988c…d81f3b
Audit this contract →
← previous block·next block →recent activity