← previous blocknext block →recent activity
Analyzing
Block #100,784,182
35 transactions · 33 stateful · 2026-08-31 14:50:20 UTC
Parallelism
80/100
Blocked
55%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,784,182 · 35 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w08w010w112w013w214w315w016w119w120w221w422w323w125w226w227w233w534w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2dfd9bc…3eec
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x513a9d01…f7a3
0x40c49f…2af0
6 touches
3 conflicts
0x25180879…8191
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xcc09e04d…81d5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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
10 conflicts on slot 0xd2dfd9bc48…fc3eec
Audit this contract →
← previous block·next block →recent activity