← previous blocknext block →recent activity
Analyzing
Block #100,584,046
35 transactions · 30 stateful · 2026-08-30 22:03:26 UTC
Parallelism
89/100
Blocked
50%
Avg conflicts / tx
0.91
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,584,046 · 35 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w18w09w111w316w217w318w019w121w222w223w026w334w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe7ad475a…0e41
0x34b655…2a6f
8 touches
6 conflicts
0x87d39100…7270
0x851145…3f07
8 touches
6 conflicts
0x24e4c4f3…60f0
0x851145…3f07
7 touches
6 conflicts
0x2de83fab…2e3f
0xd32edf…ff58
7 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xf34802b3…9f13
0x1b6862…e19c
6 touches
3 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity