← previous blocknext block →recent activity
Analyzing
Block #94,300,843
9 transactions · 9 stateful · 2026-08-08 20:32:04 UTC
Parallelism
56/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,300,843 · 9 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
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xf5ee68be…5f60
0x34b655…2a6f
6 touches
3 conflicts
0x42738dd3…8bab
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x824b4c5c…a6d0
0x34b655…2a6f
6 touches
3 conflicts
0xdcbd047a…b530
0x34b655…2a6f
5 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x0b9b07b8…b998
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…af641f
Audit this contract →
← previous block·next block →recent activity