← previous blocknext block →recent activity
Analyzing
Block #93,927,643
16 transactions · 16 stateful · 2026-08-07 13:07:54 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
1.25
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,927,643 · 16 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
1w02w13w04w15w26w38w49w410w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0a98e0d…cfae
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0x116e7d…d8f1
8 touches
6 conflicts
0x00000000…0003
0x116e7d…d8f1
8 touches
6 conflicts
0x00000000…0000
0x116e7d…d8f1
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x44ad89ba…cf83
0x350035…7777
8 touches
6 conflicts
0x692a4122…76b8
0x350035…7777
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 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
10 conflicts on slot 0xd0a98e0d76…34cfae
Audit this contract →
← previous block·next block →recent activity