← previous blocknext block →recent activity
Analyzing
Block #94,750,636
50 transactions · 24 stateful · 2026-08-10 10:24:24 UTC
Parallelism
92/100
Blocked
42%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,750,636 · 50 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
1w06w09w010w111w216w018w019w120w122w237w338w039w140w043w144w148w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xeae24c…0be0
8 touches
6 conflicts
0x2734e00b…9b4f
0x3bd359…433a
6 touches
3 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0x4aaa2679…4c1d
0x34b655…2a6f
4 touches
1 conflict
0xcce2fd99…a8eb
0x3bd359…433a
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
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: 0xeae24c72…e30be0
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity