← previous blocknext block →recent activity
Analyzing
Block #100,566,928
23 transactions · 23 stateful · 2026-08-30 20:37:19 UTC
Parallelism
65/100
Blocked
48%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,566,928 · 23 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
6w07w18w19w010w111w212w314w415w516w617w718w522w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d22c394…c125
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x33000c0a…82c3
0x34b655…2a6f
6 touches
3 conflicts
0xc820966a…3cb6
0x34b655…2a6f
6 touches
3 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
4 touches
1 conflict
0x6549c516…d8c9
0x34b655…2a6f
4 touches
1 conflict
0x88b8a8b4…5e9b
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
15 conflicts on slot 0x9d22c394fb…48c125
Audit this contract →
← previous block·next block →recent activity