← previous blocknext block →recent activity
Analyzing
Block #100,789,329
22 transactions · 21 stateful · 2026-08-31 15:16:15 UTC
Parallelism
68/100
Blocked
52%
Avg conflicts / tx
1.68
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,789,329 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w17w08w29w310w211w412w516w017w118w219w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x382434ca…96b5
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x7fafadf3…a475
0x34b655…2a6f
6 touches
3 conflicts
0x9abf5972…d759
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 0x382434ca57…4d96b5
Audit this contract →
← previous block·next block →recent activity