← previous blocknext block →recent activity
Analyzing
Block #100,266,540
20 transactions · 19 stateful · 2026-08-29 19:23:38 UTC
Parallelism
60/100
Blocked
58%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,266,540 · 20 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
1w02w14w05w19w210w311w312w414w515w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6caf33e2…c261
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x5b6af007…0f35
0x34b655…2a6f
8 touches
6 conflicts
0x41dd6ee3…0037
0x34b655…2a6f
8 touches
6 conflicts
0x1fa581e1…53d8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc2b37cdc…e470
0x34b655…2a6f
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: Perpl
15 conflicts on slot 0x6caf33e26f…3dc261
Audit this contract →
← previous block·next block →recent activity