← previous blocknext block →recent activity
Analyzing
Block #93,923,378
19 transactions · 16 stateful · 2026-08-07 12:46:27 UTC
Parallelism
68/100
Blocked
63%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,923,378 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w27w19w010w111w212w313w414w515w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d99a35e…0686
0xe52b14…7230
12 touches
15 conflicts
0x51232c8c…f30c
0xe52b14…7230
12 touches
15 conflicts
0x51232c8c…f30e
0xe52b14…7230
12 touches
15 conflicts
0xa6e37efb…afc0
0xe52b14…7230
12 touches
15 conflicts
0xa6e37efb…afc2
0xe52b14…7230
12 touches
15 conflicts
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0xec85b41e…7c91
0x1b6862…e19c
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
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: 0xe52b1424…bb7230
15 conflicts on slot 0x4d99a35e57…6d0686
Audit this contract →
← previous block·next block →recent activity