← previous blocknext block →recent activity
Analyzing
Block #100,628,303
27 transactions · 25 stateful · 2026-08-31 01:46:04 UTC
Parallelism
89/100
Blocked
32%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,628,303 · 27 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
1w02w13w04w07w09w110w112w215w117w120w223w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x5684aadd…8d62
0x34b655…2a6f
6 touches
3 conflicts
0x16d77246…bac5
0x34b655…2a6f
6 touches
3 conflicts
0x2d617a99…c997
0xd32edf…ff58
5 touches
3 conflicts
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x76832384…dc5b
0x34b655…2a6f
4 touches
1 conflict
0xbc5c1743…052c
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
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 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity