← previous blocknext block →recent activity
Analyzing
Block #99,191,179
17 transactions · 15 stateful · 2026-08-26 00:55:12 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,191,179 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w17w18w010w211w312w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18a8536c…4a40
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xe01158fd…f97e
0x1b6862…e19c
6 touches
3 conflicts
0x0fe9ce4d…1d44
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x18a8536c88…1a4a40
Audit this contract →
← previous block·next block →recent activity