← previous blocknext block →recent activity
Analyzing
Block #108,961,723
38 transactions · 30 stateful · 2026-09-29 06:12:02 UTC
Parallelism
50/100
Blocked
73%
Avg conflicts / tx
2.74
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #108,961,723 · 38 txs across 19 waves · depth 19
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
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w28w29w310w411w512w617w719w820w921w1022w1129w132w1333w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
22 touches
55 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
16 touches
28 conflicts
0x7f8e3158…9dfd
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
10 touches
10 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
10 touches
10 conflicts
0x88fc2a68…3918
0x34b655…2a6f
10 touches
10 conflicts
0xada087b9…4aca
0x34b655…2a6f
10 touches
10 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
55 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity