← previous blocknext block →recent activity
Analyzing
Block #94,301,524
14 transactions · 13 stateful · 2026-08-08 20:35:31 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,301,524 · 14 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
1w03w04w18w09w110w211w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a9e9bd1…5368
0x2a68ba…90c5
8 touches
6 conflicts
0x65058eaa…5cde
0xa6afd3…d132
7 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x11b69a7e…334e
0xee8c0e…1242
6 touches
3 conflicts
0x5261f6ab…9aa1
0xee8c0e…1242
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x3040553c…5e28
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
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: Kuru Exchange: MarginAccount
6 conflicts on slot 0x2a9e9bd1e2…355368
Audit this contract →
← previous block·next block →recent activity