← previous blocknext block →recent activity
Analyzing
Block #108,620,048
20 transactions · 20 stateful · 2026-09-28 01:27:49 UTC
Parallelism
65/100
Blocked
65%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,620,048 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w26w17w28w09w111w312w413w214w315w117w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
12 touches
15 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
10 touches
10 conflicts
0xd7fbd4e9…61ff
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xaea30221…b2bf
0x34b655…2a6f
4 touches
1 conflict
0xb5328168…9b6f
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
15 conflicts on slot 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity