← previous blocknext block →recent activity
Analyzing
Block #108,652,842
22 transactions · 21 stateful · 2026-09-28 04:12:59 UTC
Parallelism
86/100
Blocked
52%
Avg conflicts / tx
0.73
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,652,842 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w06w19w110w111w012w113w215w216w217w219w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab41643c…f9bf
0x34b655…2a6f
6 touches
3 conflicts
0x25957369…c648
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xee44a19b…7571
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
3 conflicts on slot 0xab41643cd6…d7f9bf
Audit this contract →
← previous block·next block →recent activity