← previous blocknext block →recent activity
Analyzing
Block #107,982,316
29 transactions · 26 stateful · 2026-09-25 19:57:58 UTC
Parallelism
79/100
Blocked
54%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,982,316 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w311w012w013w114w215w316w417w219w324w525w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe33bb41e…466d
0x40c49f…2af0
11 touches
15 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x6518075e…2b17
0x2a68ba…90c5
9 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xd1480c90…ae06
0x1b6862…e19c
8 touches
6 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: 0x40c49f17…d22af0
15 conflicts on slot 0xe33bb41e96…7e466d
Audit this contract →
← previous block·next block →recent activity