← previous blocknext block →recent activity
Analyzing
Block #108,533,344
31 transactions · 29 stateful · 2026-09-27 18:11:08 UTC
Parallelism
39/100
Blocked
72%
Avg conflicts / tx
6.03
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #108,533,344 · 31 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
2w03w14w25w36w47w58w69w710w811w912w1013w1114w1215w1316w1417w1524w1428w1729w18
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
34 touches
136 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
34 touches
136 conflicts
0xca841faa…486a
0x34b655…2a6f
32 touches
120 conflicts
0x5969523e…5191
0x34b655…2a6f
28 touches
91 conflicts
0x88fc2a68…3918
0x34b655…2a6f
28 touches
91 conflicts
0x9daafdf9…bb53
0x34b655…2a6f
28 touches
91 conflicts
0xa68df040…9b48
0x34b655…2a6f
28 touches
91 conflicts
0xada087b9…4aca
0x34b655…2a6f
28 touches
91 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 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity