← previous blocknext block →recent activity
Analyzing
Block #108,676,079
34 transactions · 33 stateful · 2026-09-28 06:10:00 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,676,079 · 34 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
1w02w13w04w05w17w28w09w110w213w014w015w116w217w318w419w520w627w228w332w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x125f12…a50b
14 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x348fda08…7e96
0x065c9d…c394
6 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0xbbeeffa2…2390
0x065c9d…c394
5 touches
3 conflicts
0xe1198fe3…7a10
0x065c9d…c394
5 touches
3 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: 0x125f12a1…cda50b
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity