← previous blocknext block →recent activity
Analyzing
Block #93,924,676
24 transactions · 22 stateful · 2026-08-07 12:52:59 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,924,676 · 24 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
2w03w19w010w111w212w213w314w015w416w117w221w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa608873a…c060
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x379dc435…6616
0x34b655…2a6f
6 touches
3 conflicts
0x5a100ac0…96d3
0x34b655…2a6f
6 touches
3 conflicts
0x5b6af007…0f35
0x34b655…2a6f
6 touches
3 conflicts
0x8f1df4c1…d7da
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 0xa608873a6b…86c060
Audit this contract →
← previous block·next block →recent activity