← previous blocknext block →recent activity
Analyzing
Block #93,925,509
21 transactions · 17 stateful · 2026-08-07 12:57:10 UTC
Parallelism
81/100
Blocked
41%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,925,509 · 21 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
1w03w15w27w28w311w013w115w216w017w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05114fa1…7f23
0x34b655…2a6f
8 touches
6 conflicts
0x5896e4a9…df6c
0xd32edf…ff58
7 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0xadfb5f66…2e55
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0xc13fac9b…d2cf
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0x05114fa180…b37f23
Audit this contract →
← previous block·next block →recent activity