← previous blocknext block →recent activity
Analyzing
Block #102,810,766
26 transactions · 24 stateful · 2026-09-07 17:17:13 UTC
Parallelism
69/100
Blocked
54%
Avg conflicts / tx
1.19
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,810,766 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w412w313w414w515w616w717w325w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38dea865…04dd
0x40c49f…2af0
11 touches
15 conflicts
0x3e1e8e54…9c83
0x2a68ba…90c5
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x6b2efa8d…f6ab
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x14d1bf0e…e09c
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 0x38dea86551…0804dd
Audit this contract →
← previous block·next block →recent activity