← previous blocknext block →recent activity
Analyzing
Block #106,273,350
15 transactions · 14 stateful · 2026-09-19 20:32:50 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,273,350 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfda729a6…3a4e
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x024b482b…16b0
0x34b655…2a6f
2 touches
0 conflicts
0x0e4c2ecd…9581
0x34b655…2a6f
2 touches
0 conflicts
0x11d4fcce…6d2d
0x34b655…2a6f
2 touches
0 conflicts
0x12960d2c…99f9
0x34b655…2a6f
2 touches
0 conflicts
0x2249932e…474a
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: Perpl
1 conflict on slot 0xfda729a6e6…be3a4e
Audit this contract →
← previous block·next block →recent activity