← previous blocknext block →recent activity
Analyzing
Block #94,915,019
19 transactions · 18 stateful · 2026-08-11 00:11:33 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,915,019 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w213w014w115w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
12 touches
15 conflicts
0x00000000…004c
0x80c745…7210
12 touches
15 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xbdd00e0c…6bda
0x065c9d…c394
4 touches
1 conflict
0x10f6ad02…d262
0x34b655…2a6f
2 touches
0 conflicts
0x91b0f8ed…6bd6
0x34b655…2a6f
2 touches
0 conflicts
0x91b0f8ed…6bd7
0x34b655…2a6f
2 touches
0 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: 0x80c74517…647210
15 conflicts on slot 0x0000000000…00004b
Audit this contract →
← previous block·next block →recent activity