← previous blocknext block →recent activity
Analyzing
Block #99,974,515
20 transactions · 19 stateful · 2026-08-28 18:52:01 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,974,515 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w010w011w112w213w414w515w616w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6dedaff6…161b
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c1
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x09ad83be…79ff
0x34b655…2a6f
8 touches
6 conflicts
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 0x6dedaff684…2d161b
Audit this contract →
← previous block·next block →recent activity