← previous blocknext block →recent activity
Analyzing
Block #93,573,789
18 transactions · 18 stateful · 2026-08-06 07:28:31 UTC
Parallelism
72/100
Blocked
28%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,573,789 · 18 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
5w09w110w211w312w413w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x6b7f85dc…7e36
0x34b655…2a6f
6 touches
3 conflicts
0x99c5409a…25b7
0x34b655…2a6f
6 touches
3 conflicts
0xdf00e2d7…5ada
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x6254804c…a03b
0x34b655…2a6f
4 touches
1 conflict
0x748ce49f…a12c
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity