← previous blocknext block →recent activity
Analyzing
Block #93,444,624
19 transactions · 19 stateful · 2026-08-05 20:39:12 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,444,624 · 19 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
3w04w06w18w09w110w211w112w213w314w316w417w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4f9cac7…fd98
0x34b655…2a6f
10 touches
10 conflicts
0x66a11a3b…0ee9
0xa6afd3…d132
8 touches
6 conflicts
0x103be197…826c
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x977f2411…89f7
0x34b655…2a6f
4 touches
1 conflict
0x1bde9f7f…c070
0x34b655…2a6f
4 touches
1 conflict
0x5502e1cc…3910
0x34b655…2a6f
4 touches
1 conflict
0x6530927f…68be
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
10 conflicts on slot 0xf4f9cac7d9…09fd98
Audit this contract →
← previous block·next block →recent activity