← previous blocknext block →recent activity
Analyzing
Block #99,625,992
21 transactions · 19 stateful · 2026-08-27 13:30:56 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,625,992 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w18w011w012w113w116w117w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xdb40334f…e0bc
0xa6afd3…d132
4 touches
1 conflict
0x5a7e4e98…1f3b
0x754704…b603
4 touches
1 conflict
0xd4c946a4…b8d4
0x754704…b603
4 touches
1 conflict
0x45436af6…437f
0x99c7a7…8bf0
4 touches
1 conflict
0x66300207…c47a
0x99c7a7…8bf0
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity