← previous blocknext block →recent activity
Analyzing
Block #108,681,758
22 transactions · 21 stateful · 2026-09-28 06:38:37 UTC
Parallelism
64/100
Blocked
48%
Avg conflicts / tx
1.14
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,681,758 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w29w012w113w014w016w217w318w419w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x00000000…0051
0x1b6862…e19c
4 touches
1 conflict
0x0a6cb118…4ca3
0x1b6862…e19c
4 touches
1 conflict
0xca2a5765…0390
0x1b6862…e19c
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity