← previous blocknext block →recent activity
Analyzing
Block #107,278,648
31 transactions · 27 stateful · 2026-09-23 08:54:01 UTC
Parallelism
84/100
Blocked
30%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,278,648 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w011w113w023w024w125w226w327w128w229w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x6f657889…2778
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0002
0x125f12…a50b
6 touches
3 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0009
0x125f12…a50b
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0xb7b446d2…2006
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity