← previous blocknext block →recent activity
Analyzing
Block #108,113,072
24 transactions · 24 stateful · 2026-09-26 06:55:57 UTC
Parallelism
58/100
Blocked
46%
Avg conflicts / tx
1.96
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,113,072 · 24 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w09w110w211w312w413w514w615w716w823w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92f687cb…c1db
0x34b655…2a6f
18 touches
36 conflicts
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
18 touches
36 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
16 touches
28 conflicts
0x7aa463de…e7b8
0x34b655…2a6f
16 touches
28 conflicts
0x7efbf74f…f9d2
0x34b655…2a6f
16 touches
28 conflicts
0x8714eb4d…e184
0x34b655…2a6f
16 touches
28 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
36 conflicts on slot 0x92f687cb06…bac1db
Audit this contract →
← previous block·next block →recent activity