← previous blocknext block →recent activity
Analyzing
Block #108,919,245
28 transactions · 24 stateful · 2026-09-29 02:37:14 UTC
Parallelism
36/100
Blocked
79%
Avg conflicts / tx
5.5
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #108,919,245 · 28 txs across 18 waves · depth 18
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
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w18w29w310w411w512w613w714w815w916w1017w1118w1219w220w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c29ecd5…58b6
0x34b655…2a6f
34 touches
136 conflicts
0xca841faa…486a
0x34b655…2a6f
26 touches
78 conflicts
0x93b40733…be1e
0x34b655…2a6f
26 touches
78 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
24 touches
66 conflicts
0xeb1b4ae8…64bd
0x37db7f…ec7b
24 touches
66 conflicts
0x238d0a65…428b
0x37db7f…ec7b
24 touches
66 conflicts
0x88fc2a68…3918
0x34b655…2a6f
24 touches
66 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
24 touches
66 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
136 conflicts on slot 0x4c29ecd55a…1058b6
Audit this contract →
← previous block·next block →recent activity