← previous blocknext block →recent activity
Analyzing
Block #108,655,187
22 transactions · 20 stateful · 2026-09-28 04:24:47 UTC
Parallelism
77/100
Blocked
45%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,655,187 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w110w211w312w313w414w119w020w121w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
6 touches
3 conflicts
0xb800f8a0…e30e
0x34b655…2a6f
6 touches
3 conflicts
0xbefdde57…cd0e
0x34b655…2a6f
6 touches
3 conflicts
0xc013cf15…8afd
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity