← previous blocknext block →recent activity
Analyzing
Block #93,290,753
16 transactions · 14 stateful · 2026-08-05 07:45:35 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,290,753 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w07w08w19w110w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa56e54d0…2d39
0x34b655…2a6f
6 touches
3 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
4 touches
1 conflict
0x3eebfd1c…2bf8
0x34b655…2a6f
4 touches
1 conflict
0x3de775b2…319b
0xa6afd3…d132
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7462b8f2…6312
0x34b655…2a6f
4 touches
1 conflict
0x7e1590cc…caf2
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0xa56e54d018…f82d39
Audit this contract →
← previous block·next block →recent activity