← previous blocknext block →recent activity
Analyzing
Block #107,803,812
28 transactions · 25 stateful · 2026-09-25 04:59:25 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,803,812 · 28 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
1w02w13w24w35w06w17w28w317w118w219w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x82c35368…e999
0x40c49f…2af0
12 touches
15 conflicts
0x6518075e…2b17
0x2a68ba…90c5
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0x499f1a24…1381
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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 0x82c353683a…fae999
Audit this contract →
← previous block·next block →recent activity