← previous blocknext block →recent activity
Analyzing
Block #108,655,212
21 transactions · 21 stateful · 2026-09-28 04:24:55 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,655,212 · 21 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
1w02w13w04w06w19w110w211w212w114w315w418w019w120w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbefdde57…cd0e
0x34b655…2a6f
8 touches
6 conflicts
0x939cdd56…00c8
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x0ed7cc0b…ee52
0x34b655…2a6f
4 touches
1 conflict
0x3d93ad2c…e747
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
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
6 conflicts on slot 0xbefdde5725…1dcd0e
Audit this contract →
← previous block·next block →recent activity