← previous blocknext block →recent activity
Analyzing
Block #93,338,486
19 transactions · 18 stateful · 2026-08-05 11:45:33 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,338,486 · 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
1w02w04w05w18w09w110w111w212w213w315w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc01decc3…08a1
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x3de775b2…319b
0xa6afd3…d132
6 touches
3 conflicts
0xfa551be3…a911
0xa6afd3…d132
6 touches
3 conflicts
0x2fdfa032…139c
0x34b655…2a6f
6 touches
3 conflicts
0x78f39500…290a
0x34b655…2a6f
6 touches
3 conflicts
0x859c92cc…430b
0x34b655…2a6f
6 touches
3 conflicts
0x8cb33e96…1609
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 0xc01decc387…5708a1
Audit this contract →
← previous block·next block →recent activity