← previous blocknext block →recent activity
Analyzing
Block #94,850,598
19 transactions · 17 stateful · 2026-08-10 18:47:34 UTC
Parallelism
74/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,850,598 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w06w18w29w010w111w212w313w314w418w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd51f4af1…40d5
0x968279…9342
8 touches
6 conflicts
0x521a5982…a82a
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x968279…9342
8 touches
6 conflicts
0x0875ce26…57f3
0x968279…9342
8 touches
6 conflicts
0x0875ce26…57f4
0x968279…9342
8 touches
6 conflicts
0x0875ce26…57f6
0x968279…9342
8 touches
6 conflicts
0xd51f4af1…40ce
0x968279…9342
8 touches
6 conflicts
0xd51f4af1…40cf
0x968279…9342
8 touches
6 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: 0x96827978…f09342
6 conflicts on slot 0xd51f4af179…f840d5
Audit this contract →
← previous block·next block →recent activity