← previous blocknext block →recent activity
Analyzing
Block #93,440,349
20 transactions · 19 stateful · 2026-08-05 20:17:42 UTC
Parallelism
60/100
Blocked
47%
Avg conflicts / tx
0.9
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #93,440,349 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w27w39w410w511w614w115w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99c5409a…25b7
0x34b655…2a6f
8 touches
6 conflicts
0xf4f9cac7…fd98
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xcf005309…1129
0x34b655…2a6f
6 touches
3 conflicts
0x0dfbb457…baaf
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x99c5409a28…0025b7
Audit this contract →
← previous block·next block →recent activity