← previous blocknext block →recent activity
Analyzing
Block #106,951,346
36 transactions · 31 stateful · 2026-09-22 05:26:11 UTC
Parallelism
89/100
Blocked
52%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,951,346 · 36 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
1w02w14w05w16w28w09w113w015w116w219w020w121w122w226w127w229w330w333w134w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xe03f7a66…fb46
0x34b655…2a6f
6 touches
3 conflicts
0x6c3d7137…b529
0x34b655…2a6f
6 touches
3 conflicts
0x8f18c248…9da5
0x34b655…2a6f
6 touches
3 conflicts
0xb1425636…0492
0x34b655…2a6f
6 touches
3 conflicts
0xc4c059d8…185d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd1b40f29…9b9d
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 0x49b9fdd5ff…6f9c16
Audit this contract →
← previous block·next block →recent activity