← previous blocknext block →recent activity
Analyzing
Block #99,494,299
80 transactions · 78 stateful · 2026-08-27 02:21:02 UTC
Parallelism
96/100
Blocked
6%
Avg conflicts / tx
0.07
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,494,299 · 80 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
2w03w14w26w010w177w278w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ecd29e7…e900
0x34b655…2a6f
6 touches
3 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x55010ec8…ea31
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0xa5595deb…ea31
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0x6ecd29e7c1…3ae900
Audit this contract →
← previous block·next block →recent activity