← previous blocknext block →recent activity
Analyzing
Block #106,155,048
24 transactions · 22 stateful · 2026-09-19 10:37:22 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,155,048 · 24 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
1w02w13w25w16w210w011w112w215w016w117w218w321w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5384ceb…f5bb
0x73ca90…1130
8 touches
6 conflicts
0xd5384ceb…f5bc
0x73ca90…1130
8 touches
6 conflicts
0x0768d4dc…e3ba
0x6f6493…b480
7 touches
6 conflicts
0x10deabc8…e3cd
0x6f6493…b480
7 touches
6 conflicts
0x158b867f…b33e
0x6f6493…b480
7 touches
6 conflicts
0x1902c650…ec24
0x6f6493…b480
7 touches
6 conflicts
0x1a0f4fcb…2290
0x6f6493…b480
7 touches
6 conflicts
0x1bd161f9…8beb
0x6f6493…b480
7 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: 0x73ca9094…0c1130
6 conflicts on slot 0xd5384ceb51…cff5bb
Audit this contract →
← previous block·next block →recent activity