← previous blocknext block →recent activity
Analyzing
Block #108,642,036
16 transactions · 15 stateful · 2026-09-28 03:18:35 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,642,036 · 16 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
1w02w13w19w210w213w014w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
10 touches
10 conflicts
0xc1e023aa…e9e5
0x34b655…2a6f
8 touches
6 conflicts
0x8255515e…0f8c
0x34b655…2a6f
6 touches
3 conflicts
0xdacb24f7…56ce
0x34b655…2a6f
6 touches
3 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa69bb4e1…f2bb
0x34b655…2a6f
4 touches
1 conflict
0xd739490d…821e
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
10 conflicts on slot 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity