← previous blocknext block →recent activity
Analyzing
Block #94,912,967
23 transactions · 23 stateful · 2026-08-11 00:01:14 UTC
Parallelism
87/100
Blocked
35%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,912,967 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w09w010w111w214w015w116w219w020w121w222w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85a88798…f85e
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xce06a0f7…efef
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x2110443f…0e03
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
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 0x85a88798de…47f85e
Audit this contract →
← previous block·next block →recent activity