← previous blocknext block →recent activity
Analyzing
Block #99,877,159
22 transactions · 20 stateful · 2026-08-28 10:41:24 UTC
Parallelism
82/100
Blocked
40%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,877,159 · 22 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
1w03w14w05w18w09w012w113w215w316w017w118w220w021w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fce7a05…d778
0x34b655…2a6f
6 touches
3 conflicts
0xdd6538fb…2b3f
0x34b655…2a6f
6 touches
3 conflicts
0xed903df2…6ea4
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x3293a887…43fd
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0x6fce7a0516…35d778
Audit this contract →
← previous block·next block →recent activity