← previous blocknext block →recent activity
Analyzing
Block #100,791,911
48 transactions · 41 stateful · 2026-08-31 15:29:15 UTC
Parallelism
88/100
Blocked
44%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,791,911 · 48 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
1w02w13w04w19w210w315w016w219w321w022w123w224w325w427w132w533w140w344w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
10 touches
10 conflicts
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0x474863cb…9ca3
0x851145…3f07
9 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd25997d0…a685
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity