← previous blocknext block →recent activity
Analyzing
Block #93,502,600
22 transactions · 19 stateful · 2026-08-06 01:30:39 UTC
Parallelism
77/100
Blocked
26%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,502,600 · 22 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
4w09w110w212w313w014w015w119w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed880503…9382
0x34b655…2a6f
8 touches
6 conflicts
0x808129fc…f97d
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x19e49883…3293
0x851145…3f07
4 touches
1 conflict
0xfb874a6c…caa0
0x34b655…2a6f
4 touches
1 conflict
0xac418da1…0b33
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: Perpl
6 conflicts on slot 0xed88050326…c49382
Audit this contract →
← previous block·next block →recent activity