← previous blocknext block →recent activity
Analyzing
Block #106,036,006
19 transactions · 19 stateful · 2026-09-19 00:38:16 UTC
Parallelism
63/100
Blocked
37%
Avg conflicts / tx
0.68
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,036,006 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w18w29w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ee73aa5…0d70
0x34b655…2a6f
8 touches
6 conflicts
0xa2a82506…1320
0x34b655…2a6f
8 touches
6 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
6 touches
3 conflicts
0x99ea3e3c…a2d6
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd58e5c6b…7188
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf726e2e2…e561
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x9ee73aa569…a00d70
Audit this contract →
← previous block·next block →recent activity