← previous blocknext block →recent activity
Analyzing
Block #106,308,244
22 transactions · 21 stateful · 2026-09-19 23:28:24 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,308,244 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w010w011w112w213w316w119w020w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a254d1c…508c
0x73ca90…1130
8 touches
6 conflicts
0x07e864fa…1537
0x6f6493…b480
8 touches
6 conflicts
0xb4e9ce6c…bc2b
0x6f6493…b480
8 touches
6 conflicts
0xd2d46a81…cb3f
0x6f6493…b480
8 touches
6 conflicts
0xfa07ad9a…008c
0x6f6493…b480
8 touches
6 conflicts
0x3a254d1c…508b
0x73ca90…1130
8 touches
6 conflicts
0x142f15cc…ba11
0x6f6493…b480
8 touches
6 conflicts
0x1d8d053d…88ec
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: 0x73ca9094…0c1130
6 conflicts on slot 0x3a254d1ce3…0c508c
Audit this contract →
← previous block·next block →recent activity