← previous blocknext block →recent activity
Analyzing
Block #99,248,488
13 transactions · 12 stateful · 2026-08-26 05:43:32 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,248,488 · 13 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
1w02w13w26w07w312w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x556beb43…e627
0x34b655…2a6f
6 touches
3 conflicts
0x90f65937…f295
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0xb7e8b0c4…dec3
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x7aa463de…e7b8
0x34b655…2a6f
4 touches
1 conflict
0x887e9867…1258
0x34b655…2a6f
4 touches
1 conflict
0x9d6a99f9…da64
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
3 conflicts on slot 0x556beb4322…c0e627
Audit this contract →
← previous block·next block →recent activity