← previous blocknext block →recent activity
Analyzing
Block #100,584,693
24 transactions · 23 stateful · 2026-08-30 22:06:41 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,584,693 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w16w28w011w112w213w114w015w218w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x216154bf…b55c
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xb4c703ab…f8cf
0x34b655…2a6f
6 touches
3 conflicts
0x9d929e0c…9421
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x16d77246…bac5
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xf38a3927…ad62
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
3 conflicts on slot 0x216154bf3f…a8b55c
Audit this contract →
← previous block·next block →recent activity