← previous blocknext block →recent activity
Analyzing
Block #100,567,622
25 transactions · 21 stateful · 2026-08-30 20:40:48 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
1.04
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,567,622 · 25 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
1w02w14w05w16w17w08w19w011w114w215w317w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x41f621e0…9e98
0x34b655…2a6f
10 touches
10 conflicts
0xf38a3927…ad62
0x34b655…2a6f
8 touches
6 conflicts
0x72083f0d…082a
0x34b655…2a6f
8 touches
6 conflicts
0xd814f518…f5b4
0x34b655…2a6f
7 touches
6 conflicts
0x94e7f277…471b
0x34b655…2a6f
6 touches
3 conflicts
0x310a7246…2dcb
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity