← previous blocknext block →recent activity
Analyzing
Block #108,674,213
32 transactions · 30 stateful · 2026-09-28 06:00:37 UTC
Parallelism
72/100
Blocked
60%
Avg conflicts / tx
1.5
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #108,674,213 · 32 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w17w29w310w411w512w013w116w618w120w422w623w425w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0xdbcb2275…306e
0xd32edf…ff58
9 touches
10 conflicts
0xc3e72796…a3ca
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x6235638c…6436
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb80
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity