← previous blocknext block →recent activity
Analyzing
Block #100,587,631
30 transactions · 24 stateful · 2026-08-30 22:21:28 UTC
Parallelism
77/100
Blocked
46%
Avg conflicts / tx
0.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,587,631 · 30 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
1w02w13w04w16w27w38w09w111w316w417w518w019w621w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8d7f73d…a566
0x34b655…2a6f
8 touches
6 conflicts
0x3bfb961d…1dee
0x34b655…2a6f
8 touches
6 conflicts
0x8311570f…5321
0x34b655…2a6f
6 touches
3 conflicts
0x0b3eb43a…ca08
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x9c6a9da2…c628
0x34b655…2a6f
6 touches
3 conflicts
0xe61ddaa5…60a2
0xd32edf…ff58
5 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
6 conflicts on slot 0xc8d7f73de9…d9a566
Audit this contract →
← previous block·next block →recent activity