← previous blocknext block →recent activity
Analyzing
Block #100,606,269
24 transactions · 20 stateful · 2026-08-30 23:55:14 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,606,269 · 24 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
2w03w04w17w18w010w114w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b305b76…44c5
0x34b655…2a6f
6 touches
3 conflicts
0x8649e48f…941c
0xc8689a…ee79
4 touches
1 conflict
0x0ed7cc0b…ee52
0x34b655…2a6f
4 touches
1 conflict
0xa169711f…c7f3
0x34b655…2a6f
4 touches
1 conflict
0xb5c7c6aa…fdba
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xe5eb3c33…0e3a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
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 0x5b305b7663…df44c5
Audit this contract →
← previous block·next block →recent activity