← previous blocknext block →recent activity
Analyzing
Block #106,035,326
13 transactions · 13 stateful · 2026-09-19 00:34:51 UTC
Parallelism
85/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,035,326 · 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
2w03w17w08w19w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeedc3757…d58c
0x99c7a7…8bf0
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x2e77b2d0…090f
0x34b655…2a6f
4 touches
1 conflict
0xd62f3741…b903
0x34b655…2a6f
4 touches
1 conflict
0x25ccb625…335f
0x754704…b603
4 touches
1 conflict
0xb5c1d5f6…712d
0x754704…b603
4 touches
1 conflict
0xcabfddb7…542b
0x754704…b603
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: 0x99c7a72e…c78bf0
1 conflict on slot 0xeedc3757a5…c0d58c
Audit this contract →
← previous block·next block →recent activity