← previous blocknext block →recent activity
Analyzing
Block #99,937,539
16 transactions · 16 stateful · 2026-08-28 15:45:41 UTC
Parallelism
50/100
Blocked
44%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,937,539 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w47w58w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x6bab0076…422b
0x34b655…2a6f
4 touches
1 conflict
0x805d08cf…3cfc
0x34b655…2a6f
4 touches
1 conflict
0x82e80565…ebce
0x34b655…2a6f
4 touches
1 conflict
0xc52cc97a…a106
0x34b655…2a6f
4 touches
1 conflict
0xad3e66be…dccc
0xc8689a…ee79
4 touches
1 conflict
0x15698ac9…2a46
0x34b655…2a6f
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity