← previous blocknext block →recent activity
Analyzing
Block #100,589,827
32 transactions · 25 stateful · 2026-08-30 22:32:30 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,589,827 · 32 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
1w04w06w08w112w113w016w123w125w226w228w029w130w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x76622fb2…4f08
0x34b655…2a6f
6 touches
3 conflicts
0xb409e204…89ac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x79347b24…9fba
0x34b655…2a6f
4 touches
1 conflict
0xc26b872e…7917
0x34b655…2a6f
4 touches
1 conflict
0x39773cec…38ed
0xa6afd3…d132
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity