← previous blocknext block →recent activity
Analyzing
Block #94,901,044
37 transactions · 34 stateful · 2026-08-10 23:01:16 UTC
Parallelism
78/100
Blocked
71%
Avg conflicts / tx
1.73
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,901,044 · 37 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w17w28w09w110w111w215w319w420w321w323w425w526w427w632w533w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a57a2b8…3cdd
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x3464bbc5…a323
0xa6afd3…d132
8 touches
6 conflicts
0x23d51e55…82c2
0x34b655…2a6f
8 touches
6 conflicts
0x348aad9f…93e1
0xd32edf…ff58
7 touches
6 conflicts
0x01a056f8…64e4
0x34b655…2a6f
6 touches
3 conflicts
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
21 conflicts on slot 0x0a57a2b8cd…773cdd
Audit this contract →
← previous block·next block →recent activity