← previous blocknext block →recent activity
Analyzing
Block #106,337,268
16 transactions · 16 stateful · 2026-09-20 01:54:28 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,337,268 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w08w19w210w312w114w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01bd5b1c…f8a6
0x6f6493…b480
8 touches
6 conflicts
0x13be483e…97a7
0x6f6493…b480
8 touches
6 conflicts
0x1466adc3…3816
0x6f6493…b480
8 touches
6 conflicts
0x174cce33…d1bc
0x6f6493…b480
8 touches
6 conflicts
0x1837b5bb…ad55
0x6f6493…b480
8 touches
6 conflicts
0x1ac02261…6c34
0x6f6493…b480
8 touches
6 conflicts
0x1bd6e9ae…a331
0x6f6493…b480
8 touches
6 conflicts
0x1dd0dbcf…f2a4
0x6f6493…b480
8 touches
6 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: 0x6f6493e3…08b480
6 conflicts on slot 0x01bd5b1c6e…8bf8a6
Audit this contract →
← previous block·next block →recent activity