← previous blocknext block →recent activity
Analyzing
Block #93,238,436
21 transactions · 19 stateful · 2026-08-05 03:22:31 UTC
Parallelism
71/100
Blocked
53%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,238,436 · 21 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
2w04w15w06w17w28w39w010w111w312w416w517w018w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x90c6414a…4aec
0x34b655…2a6f
8 touches
6 conflicts
0x291ad0b4…69e9
0x34b655…2a6f
6 touches
3 conflicts
0xa169711f…c7f3
0x34b655…2a6f
4 touches
1 conflict
0xa86351b8…2c5a
0x34b655…2a6f
4 touches
1 conflict
0xb371802a…310c
0x34b655…2a6f
4 touches
1 conflict
0xbd26d3a7…f31a
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity