← previous blocknext block →recent activity
Analyzing
Block #93,074,642
13 transactions · 12 stateful · 2026-08-04 13:38:07 UTC
Parallelism
69/100
Blocked
25%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,074,642 · 13 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
1w02w13w04w08w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb5d573d…ab76
0x34b655…2a6f
4 touches
1 conflict
0xb8ce1c1c…16b5
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc6acd1d6…2330
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xcd26fba5…21c6
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
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
1 conflict on slot 0xeb5d573dbe…35ab76
Audit this contract →
← previous block·next block →recent activity