← previous blocknext block →recent activity
Analyzing
Block #100,139,051
9 transactions · 9 stateful · 2026-08-29 08:40:33 UTC
Parallelism
67/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,139,051 · 9 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
4w05w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37b6ab99…7682
0x34b655…2a6f
4 touches
1 conflict
0x54f7f60f…43cc
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
2 touches
0 conflicts
0x5778d110…d2e6
0xc8689a…ee79
2 touches
0 conflicts
0x02c556ef…e0e8
0xe52b14…7230
2 touches
0 conflicts
0x02c556ef…e0ea
0xe52b14…7230
2 touches
0 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
1 conflict on slot 0x37b6ab997e…dd7682
Audit this contract →
← previous block·next block →recent activity