← previous blocknext block →recent activity
Analyzing
Block #93,227,796
19 transactions · 15 stateful · 2026-08-05 02:29:02 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,227,796 · 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
3w09w010w111w013w214w115w116w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1a287886…0266
0xa6afd3…d132
4 touches
1 conflict
0xd9a117fc…2349
0x34b655…2a6f
4 touches
1 conflict
0xd9a117fc…234a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x1803586e…d149
0xa6afd3…d132
4 touches
1 conflict
0x388b63a9…5008
0x34b655…2a6f
4 touches
1 conflict
0x4acbdbcf…a8c6
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity