← previous blocknext block →recent activity
Analyzing
Block #106,184,933
17 transactions · 17 stateful · 2026-09-19 13:07:45 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,184,933 · 17 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
1w02w03w14w15w27w08w110w212w013w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x040a9f57…363b
0x6f6493…b480
8 touches
6 conflicts
0x07c7cf70…a528
0x6f6493…b480
8 touches
6 conflicts
0x093955dc…eb61
0x6f6493…b480
8 touches
6 conflicts
0x0a4d4ecc…4014
0x6f6493…b480
8 touches
6 conflicts
0x0fce0435…6620
0x6f6493…b480
8 touches
6 conflicts
0x10f4b037…0514
0x6f6493…b480
8 touches
6 conflicts
0x11b9cc5b…fc95
0x6f6493…b480
8 touches
6 conflicts
0x1255e5ae…b357
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 0x040a9f577e…91363b
Audit this contract →
← previous block·next block →recent activity