← previous blocknext block →recent activity
Analyzing
Block #100,786,082
25 transactions · 24 stateful · 2026-08-31 14:59:54 UTC
Parallelism
64/100
Blocked
42%
Avg conflicts / tx
1.28
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,786,082 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w08w19w212w314w416w517w618w220w724w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xce74d807…8716
0x34b655…2a6f
10 touches
10 conflicts
0x3ee8b564…4c49
0x34b655…2a6f
6 touches
3 conflicts
0x39773cec…38ed
0xa6afd3…d132
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xef3f5637…f47c
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity