← previous blocknext block →recent activity
Analyzing
Block #108,919,147
35 transactions · 33 stateful · 2026-09-29 02:36:44 UTC
Parallelism
54/100
Blocked
58%
Avg conflicts / tx
3.51
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #108,919,147 · 35 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w27w08w19w210w311w412w513w614w715w821w228w929w1031w1232w1333w1434w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c29ecd5…58b6
0x34b655…2a6f
30 touches
105 conflicts
0xeb1b4ae8…64bd
0x37db7f…ec7b
18 touches
36 conflicts
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
18 touches
36 conflicts
0x93b40733…be1e
0x34b655…2a6f
18 touches
36 conflicts
0xfc8c9734…8019
0x34b655…2a6f
18 touches
36 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
18 touches
36 conflicts
0x88fc2a68…3918
0x34b655…2a6f
16 touches
28 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
105 conflicts on slot 0x4c29ecd55a…1058b6
Audit this contract →
← previous block·next block →recent activity