← previous blocknext block →recent activity
Analyzing
Block #93,243,622
15 transactions · 13 stateful · 2026-08-05 03:48:36 UTC
Parallelism
53/100
Blocked
54%
Avg conflicts / tx
1.4
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,243,622 · 15 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
1w02w03w15w26w37w49w510w614w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94907e1c…f808
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xf9e23360…8ef7
0x34b655…2a6f
8 touches
6 conflicts
0x4f3a6b4a…3819
0x34b655…2a6f
8 touches
6 conflicts
0xbe10ddee…7510
0x34b655…2a6f
6 touches
3 conflicts
0x361f4a1b…1f14
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
10 conflicts on slot 0x94907e1c19…9af808
Audit this contract →
← previous block·next block →recent activity